Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: 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: Tue, 29 Aug 2006 19:08:00 -0000	[thread overview]
Message-ID: <20060829190818.GA27001@nevyn.them.org> (raw)
In-Reply-To: <200608291903.k7TJ3VPb001854@elgar.sibelius.xs4all.nl>

On Tue, Aug 29, 2006 at 09:03:31PM +0200, Mark Kettenis wrote:
> > Here's my question: why isn't that happening already?  Don't we get
> > shared library events after relocation processing?  Or do we get one
> > before and one after?
> 
> 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).

Is one of these before constructors and the other after, do you know?
How about relocation processing?  We really want to insert these
breakpoints before constructors; it's not unheard of to create a thread
in a shared library constructor.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-08-29 19:08 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 [this message]
2006-09-20 15:49     ` Daniel Jacobowitz
2006-09-20 17:41       ` John Reiser

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=20060829190818.GA27001@nevyn.them.org \
    --to=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