From: John Reiser <jreiser@BitWagon.com>
To: Daniel Jacobowitz <drow@false.org>,
Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: pgilliam@us.ibm.com, gdb@sources.redhat.com, sjmunroe@us.ibm.com
Subject: Re: breaks at thread create and delete fail on PPC64/Linux
Date: Wed, 20 Sep 2006 17:41:00 -0000 [thread overview]
Message-ID: <45117D2B.9090608@BitWagon.com> (raw)
In-Reply-To: <20060920154947.GA17599@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Tue, Aug 29, 2006 at 09:03:31PM +0200, Mark Kettenis wrote:
>
>>Normally we get an event right before a shared library and its
>>dependencies is loaded and right after. At that last event things are
>>supposed to be in a consistent state, so relocations should have been
>>processed (except for relocations to be resilved by lazy binding of
>>course).
>
>
> I happened to stumble across this bug report from John Reiser today,
> which seems to explain Paul's trouble:
> http://sourceware.org/bugzilla/show_bug.cgi?id=2328
>
> He's even got a patch for it, but it isn't in the bug report. John,
> any change that you could break it out of the other patches and submit
> it?
>
> In the mean time, it's over here:
> http://www.bitwagon.com/glibc-audit/glibc-audit.html
>
Attached in Comment #1 of
http://sourceware.org/bugzilla/show_bug.cgi?id=2328
--
John Reiser, jreiser@BitWagon.com
prev parent reply other threads:[~2006-09-20 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 23:19 PAUL GILLIAM
2006-08-28 23:22 ` Daniel Jacobowitz
2006-08-28 23:31 ` PAUL GILLIAM
2006-08-29 19:04 ` Mark Kettenis
2006-08-29 19:08 ` Daniel Jacobowitz
2006-09-20 15:49 ` Daniel Jacobowitz
2006-09-20 17:41 ` John Reiser [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=45117D2B.9090608@BitWagon.com \
--to=jreiser@bitwagon.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=pgilliam@us.ibm.com \
--cc=sjmunroe@us.ibm.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