Re: gdb + sigtraps

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

On Mon, Mar 26, 2012 at 12:01:18PM -0400, Christos Zoulas wrote:
> On Mar 26,  4:25pm, prlw1%cam.ac.uk@localhost (Patrick Welche) wrote:
> -- Subject: Re: gdb + sigtraps
> 
> | On Wed, Mar 21, 2012 at 11:36:15PM +0000, Christos Zoulas wrote:
> | > In article 
> <201203212220.q2LMK9Cn006251%ginseng.pulsar-zone.net@localhost>,
> | > Matthew Mondor  <mm_lists%pulsar-zone.net@localhost> wrote:
> | > >On Wed, 21 Mar 2012 21:38:46 +0000 (UTC)
> | > >christos%astron.com@localhost (Christos Zoulas) wrote:
> | > >
> | > >> continue does not work? Or telling gdb to ignore SIGTRAP? Made some 
> more
> | > >> progress debugging it, but gdb is a complex beast...
> | > >
> | > >continue also wasn't helpful for me then.  If I remember I managed to
> | > >make it coredump, and then I could get more information.
> | > 
> | > I think it should work now, cvs update.
> | 
> | Sadly it seems even worse: I don't set a break point, "continue" everytime
> | a sigtrap happens, and the programme run from gdb uoesn't open a gtk window,
> | whereas it does when not run inside gdb.
> 
> You should not be getting anymore sigtraps with the head of the code. Can
> you try to see if simply gdb /usr/bin/dig, break main, run, causes any traps?


I do - I did a update build with head - maybe I need to clear obj out...

quark: {1} gdb /usr/bin/dig
GNU gdb (GDB) 7.3.1
...
Reading symbols from /usr/bin/dig...(no debugging symbols found)...done.
(gdb) break main
Breakpoint 1 at 0x408b59
(gdb) run
Starting program: /usr/bin/dig 

Breakpoint 1, 0x0000000000408b59 in main ()
(gdb) c
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007f7ff58390ba in _sys___kevent50 () from /usr/lib/libc.so.12
(gdb) 


Cheers,

Patrick