Re: gdb + sigtraps

[christos%zoulas.com@localhost (Christos Zoulas)]

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?

christos