Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	        gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fixes problem setting breakpoint in dynamic loader
Date: Fri, 22 Jun 2007 14:07:00 -0000	[thread overview]
Message-ID: <1182521245.8285.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20070620142144.GA30319@caradoc.them.org>

On Wed, 2007-06-20 at 10:21 -0400, Daniel Jacobowitz wrote:
> On Wed, Jun 20, 2007 at 09:15:24AM -0400, Daniel Jacobowitz wrote:
> > Here's an extended version of Joseph's revision of Thiago's revision
> > of Paul's patch (begat by... who begat...).  I tested it with
> > gdbserver on powerpc-linux -m64; it fixes the function calling test in
> > nodebug.exp and all the threading tests.  The branch I was testing on
> > is a little bit older than HEAD, and I had an unstripped libc; but I
> > believe that on HEAD and with a stripped libc, it will also fix a
> > number of shared library load/unload tests and all of the calls to
> > malloc to create strings.  I'm going to test it natively now.
> 
> The shared library tests seem generally OK, and it fixes all sorts of
> tests that call malloc or fork.

This patch fixes my problem as well. Thanks for helping with this.

> Unless someone sees a problem with this patch, I would like to include
> it in GDB 6.7.

Me too.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center


  reply	other threads:[~2007-06-22 14:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 20:59 Thiago Jung Bauermann
2007-06-14 23:38 ` Joseph S. Myers
2007-06-20 13:15   ` Daniel Jacobowitz
2007-06-20 14:21     ` Daniel Jacobowitz
2007-06-22 14:07       ` Thiago Jung Bauermann [this message]
2007-06-20 14:39     ` Ulrich Weigand
2007-06-25 21:28     ` Ulrich Weigand
2007-07-03 15:58       ` Daniel Jacobowitz
2007-06-26 18:43     ` Joel Brobecker
  -- strict thread matches above, loose matches on Subject: below --
2006-05-25  2:26 [patch] " PAUL GILLIAM
2006-05-25 16:27 ` Daniel Jacobowitz
2006-05-25 22:58   ` PAUL GILLIAM
2006-05-25 23:12     ` Daniel Jacobowitz
2006-05-27 17:52       ` PAUL GILLIAM
2006-06-23 21:33         ` PAUL GILLIAM
2006-06-23 21:48           ` Mark Kettenis
2006-06-26 22:21             ` PAUL GILLIAM
2006-06-26 22:28             ` PAUL GILLIAM
2006-06-26 23:55               ` Kevin Buettner
2006-06-26 18:48           ` Kevin Buettner
2006-06-17 20:21 ` Mark Kettenis
2006-07-06  1:01   ` PAUL GILLIAM
2006-07-06  2:57     ` Daniel Jacobowitz
2006-07-06 16:10     ` Kevin Buettner
2006-07-16 18:57     ` Andreas Schwab
2006-07-19 21:55       ` PAUL GILLIAM
2006-05-20  6:21 [PATCH] -var-update Nick Roberts
2006-05-20 16:34 ` Daniel Jacobowitz
2006-05-21  2:04   ` Nick Roberts
2006-05-21  5:22     ` Daniel Jacobowitz
2006-05-21 23:04       ` Nick Roberts
2006-05-25  0:21         ` Nick Roberts
2006-05-25  0:26           ` [patch] Fixes problem setting breakpoint in dynamic loader PAUL GILLIAM
2006-05-25  0:29             ` PAUL GILLIAM

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=1182521245.8285.30.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.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