public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "pedro at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug threads/10757] GDB does not attach all threads of a multithreaded process => inferior gets SIGTRAP Date: Sun, 11 Oct 2009 22:33:00 -0000 [thread overview] Message-ID: <20091011223317.29471.qmail@sourceware.org> (raw) In-Reply-To: <20091011171907.10757.ppluzhnikov@google.com> ------- Additional Comments From pedro at codesourcery dot com 2009-10-11 22:33 ------- Subject: Re: GDB does not attach all threads of a multithreaded process => inferior gets SIGTRAP Also, if you let the app that crashed with a SIGTRAP dump core, you could load its core into gdb to check which breakpoint trapped (well, the address of the breakpoint). Remember to disable address space randomization to make your life easier. -- 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.
next prev parent reply other threads:[~2009-10-11 22:33 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-11 17:19 [Bug threads/10757] New: " ppluzhnikov at google dot com 2009-10-11 17:22 ` [Bug threads/10757] " ppluzhnikov at google dot com 2009-10-11 21:47 ` ppluzhnikov at google dot com 2009-10-11 22:28 ` pedro at codesourcery dot com 2009-10-11 22:33 ` pedro at codesourcery dot com [this message] 2009-10-11 23:27 ` ppluzhnikov at google dot com 2009-10-11 23:51 ` pedro at codesourcery dot com 2009-10-12 0:56 ` pedro at codesourcery dot com 2009-10-12 1:10 ` pedro at codesourcery dot com 2009-10-12 10:40 ` jan dot kratochvil at redhat dot com 2009-10-15 18:17 ` cvs-commit at gcc dot gnu dot org 2009-10-27 21:33 ` cvs-commit at gcc dot gnu dot org 2009-10-28 17:03 ` cvs-commit at gcc dot gnu dot org 2009-10-31 15:05 ` pedro at codesourcery dot com 2009-10-31 17:26 ` ppluzhnikov at google dot com 2009-12-08 17:11 ` ppluzhnikov at google dot com 2009-12-08 17:19 ` esigra at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20091011223317.29471.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).