Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>,
		Thiago Jung Bauermann <bauerman@br.ibm.com>,
		gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fixes problem setting breakpoint in dynamic loader
Date: Tue, 26 Jun 2007 18:43:00 -0000	[thread overview]
Message-ID: <20070626183744.GE3700@adacore.com> (raw)
In-Reply-To: <20070620131524.GA21190@caradoc.them.org>

Daniel,

You said you wanted this to be part of 6.7. Ulrich said it looked OK,
so can we commit this patch sometime soon?

> 2007-06-20  Paul Gilliam  <pgilliam@us.ibm.com>
> 	    Thiago Bauermann  <bauerman@br.ibm.com>
> 	    Joseph S. Myers  <joseph@codesourcery.com>
> 	    Daniel Jacobowitz  <dan@codesourcery.com>
> 
> 	gdb/
> 	* remote.c (remote_check_symbols): Use
> 	gdbarch_convert_from_func_ptr_addr.
> 	* infcall.c (find_function_addr): Handle function descriptors
> 	without debugging information.
> 	* ppc-linux-tdep.c (ppc_linux_convert_from_func_ptr_addr): Renamed
> 	from ppc64_linux_convert_from_func_ptr_addr.  Handle -msecure-plt.
> 	(ppc_linux_init_abi): Always set convert_from_func_ptr_addr.
> 	* solib-svr4.c (solib_break_names): Remove "._dl_debug_state".
> 	(bfd_lookup_symbol): Do not take a SECT_FLAGS argument.  Always
> 	allow SEC_CODE and SEC_DATA.
> 	(enable_break): Update calls.  Pass current_target to solib_add.
> 	Use gdbarch_convert_from_func_ptr_addr.
> 
> 	gdb/gdbserver/
> 	* remote-utils.c (look_up_one_symbol): Handle 'm' packets.

Thanks,
-- 
Joel


  parent reply	other threads:[~2007-06-26 18:35 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
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 [this message]
  -- 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=20070626183744.GE3700@adacore.com \
    --to=brobecker@adacore.com \
    --cc=bauerman@br.ibm.com \
    --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