This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug threads/10757] GDB does not attach all threads of a multithreaded process => inferior gets SIGTRAP


------- Additional Comments From pedro at codesourcery dot com  2009-10-12 01:10 -------
Subject: Re:  GDB does not attach all threads of a multithreaded process => inferior gets SIGTRAP

On Monday 12 October 2009 01:56:10, pedro at codesourcery dot com wrote:

> On my machine (ubuntu 8.04, 2.6.24-24-generic x86_64) I haven't
> managed to get a SIGTRAP, but I see badness nonetheless.

Bah, update: I've just gotten a SIGTRAP.  I just needed:

 "attach; b foo; c"

Indeed I never see the problem when I do 

 "attach; info threads; b foo; c"

Sorry for not having confirmed what was going on
before digressing into breakpoint insertion issues.  :-)

Sometimes I also see this when attaching...:

 warning: Can't attach LWP 15338: No such process
 ../../src/gdb/linux-nat.c:1341: internal-error: linux_nat_post_attach_wait: Assertion `pid == new_pid && WIFSTOPPED (status)' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.
 Quit this debugging session? (y or n)     

It seems that the first event we get right after PTRACE_ATTACH can be an
lwp exit.



-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10757

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]