On Mon, 23 Jun 2003 weppnesp@eckerd.edu wrote:
it got caught in thread purgatory, do i need to debug with a special
option for static?
You could try "handle SIGRT32 nostop noprint" at the gdb prompt.
109 code = (*fs.personality) (1, _UA_SEARCH_PHASE, exc->exception_class,
(gdb)
Program received signal SIGSEGV, Segmentation fault.
0x00006000 in ?? ()
Now that is strange... looks as though it cannot reach the personality
routine. When compiling with -fPIC, the unwind info looks like:
.byte 0x9b # Personality (indirect pcrel sdata4)
.long DW.ref.__gcj_personality_v0-.
...
.hidden DW.ref.__gcj_personality_v0
.weak DW.ref.__gcj_personality_v0
DW.ref.__gcj_personality_v0:
.long __gcj_personality_v0
Your crash is as if pc-relative unwind data isn't decoded properly. But
this configuration seems to work for others, so... I really can't say
what's going wrong.
Jeff