From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Jeff Kenton <jkenton@tilera.com>
Subject: Re: GDB problems with pthread_join()
Date: Wed, 26 Oct 2011 15:56:00 -0000 [thread overview]
Message-ID: <201110261548.49941.pedro@codesourcery.com> (raw)
In-Reply-To: <4EA5C49B.5000302@tilera.com>
On Monday 24 October 2011 21:03:39, Jeff Kenton wrote:
>
> I have gdb-7.1 mostly working on our two processors (one is 32-bit, the
> other 64-bit). With a trivial pthread program running under GDB with no
> breakpoints set, it runs to completion on one machine (32-bit) but hangs
> on the other with:
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> [Switching to Thread 0xaaab54f200 (LWP 721)]
> 0x000000aaaab09e58 in pthread_join (threadid=733018911232,
> thread_return=0x0)
> at pthread_join.c:89
>
> The SIGTRAP could be GDB's hook into the pthread library but I'm not
> sure. Other SIGTRAPs succeed happily (traced with set debug infrun 1).
"maint info breakpoints" shows the addresses of thread event
breakpoints, if your port uses those.
> Any clues? Anyone seen this before? Thoughts besides "sounds nasty and
> you'll have to figure it out yourself"?
There's not much information in your email to go by, but similar
weird things can happen if you use a 32-bit gdb to debug a 64-bit
program on other archs. If that's the case, try building a 64-bit
gdb for the 64-bit machine. If not, assuming you're native linux,
maybe "set debug lin-lwp 1" casts some more light. Good luck.
--
Pedro Alves
prev parent reply other threads:[~2011-10-26 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 21:06 Jeff Kenton
2011-10-26 15:56 ` Pedro Alves [this message]
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=201110261548.49941.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=jkenton@tilera.com \
/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: link
Be 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).