From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: schwab@suse.de
Cc: gdb@sourceware.org
Subject: Re: How to avoid stepping inside libpthread
Date: Thu, 12 Jul 2007 02:15:00 -0000 [thread overview]
Message-ID: <20070712.111540.126572286.nemoto@toshiba-tops.co.jp> (raw)
In-Reply-To: <jelkdnfh81.fsf@sykes.suse.de>
On Wed, 11 Jul 2007 10:59:58 +0200, Andreas Schwab <schwab@suse.de> wrote:
> > There is a LL/SC loop (atomic_decrement_and_test(&__nptl_nthreads))
> > after the 0x2ab0ae88 in start_thread(), so it is not wonder the single
> > stepping never ends (SC always fail due to a breakpoint exception).
> >
> >
> > Are there any way to avoid falling into such situations?
>
> See deal_with_atomic_sequence in rs6000-tdep.c, which tries to solve the
> same issue.
Thank you. I'll try to implement the feature for mips.
---
Atsushi Nemoto
next prev parent reply other threads:[~2007-07-12 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 6:18 Atsushi Nemoto
2007-07-11 9:00 ` Andreas Schwab
2007-07-12 2:15 ` Atsushi Nemoto [this message]
2007-07-12 6:31 ` Atsushi Nemoto
2007-07-12 11:10 ` Daniel Jacobowitz
2007-07-13 7:04 ` Atsushi Nemoto
2007-09-26 21:06 ` Daniel Jacobowitz
2007-07-11 11:40 ` Daniel Jacobowitz
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=20070712.111540.126572286.nemoto@toshiba-tops.co.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=gdb@sourceware.org \
--cc=schwab@suse.de \
/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