Operating System - Linux
1753420 Members
4729 Online
108793 Solutions
New Discussion юеВ

GDB failed with SIGILL when set breakpoint

 
joyo
Occasional Contributor

GDB failed with SIGILL when set breakpoint

Newbie in HPUX development. I write a simple c program ,just print Hello. It runs well. But if i use gdb debug it, if i set breakpoints , and run it ,gdb will stop with signals.The output is :
"Program received signal SIGILL ,Illegal instruction si_code=8 - ILL_ILLOPC - Illegal Op-Code. 0x400000002314 in main() at test.c:3
3 { " So, i cannot debug my application with gdb. What's wrong?How can i fix it?
Gcc --version 4.0.3
gcc -v using built-in specs Target:hppa64-hp-hpux11.11
gdb HP GDB 5.4.0 for PA-RISC 1.1 or 2.0 ,HP-UX 11.00 and target hppa1.1-hp-hpux11.00
5 REPLIES 5
Dennis Handly
Acclaimed Contributor

Re: GDB failed with SIGILL when set breakpoint

It appears you are using gcc with HP's gdb. You may have to download a newer gdb:
http://www.hp.com/go/wdb
Mithun R N
Advisor

Re: GDB failed with SIGILL when set breakpoint

Hi:

There have been some more support provided on the latest HP-WDB for gcc binaries on PA64, and more specifically I think your problem is also fixed.

Mithun
Dennis Handly
Acclaimed Contributor

Re: GDB failed with SIGILL when set breakpoint

Some of the problems that Mithun mentioned are:
JAGaf63546 issues in debugging gcc compiled executables
JAGag23001 Problems unwinding from gcc frames
JAGag22995 gcc debugee crashes when run within gdb
joyo
Occasional Contributor

Re: GDB failed with SIGILL when set breakpoint

thanks for u quick answer. But what is JAGaf6354 ? Can u show me the link?
Dennis Handly
Acclaimed Contributor

Re: GDB failed with SIGILL when set breakpoint

>But what is JAGaf6354? Can you show me the link?

You were suppose to just get the latest gdb because you were scared. ;-)

JAGaf6354 is the ID of the bug. The description may have helped. You can't see them unless you have a support contract.