From: Daniel Jacobowitz <drow@false.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, gdb-patches@sources.redhat.com
Cc: jvh@tivo.com, gdb@sources.redhat.com
Subject: Re: gdb 6.x 'next' does not work on mips-linux/mipsel-linux
Date: Mon, 09 May 2005 03:36:00 -0000 [thread overview]
Message-ID: <20050509033631.GA31464@nevyn.them.org> (raw)
In-Reply-To: <20050509.121635.85420824.nemoto@toshiba-tops.co.jp>
On Mon, May 09, 2005 at 12:16:35PM +0900, Atsushi Nemoto wrote:
> >>>>> On Wed, 27 Apr 2005 10:17:14 -0400, Daniel Jacobowitz <drow@false.org> said:
> drow> 2005-04-27 Daniel Jacobowitz <dan@codesourcery.com>
>
> drow> * mips-tdep.c (mips_stub_frame_sniffer): Handle .MIPS.stubs
> drow> section like .plt.
>
> This fix still not be checked in. Is there any problem with this
> patch?
None; I forgot about it! Sorry.
I have checked in the attached.
--
Daniel Jacobowitz
CodeSourcery, LLC
2005-05-08 Daniel Jacobowitz <dan@codesourcery.com>
* mips-tdep.c (mips_stub_frame_sniffer): Handle .MIPS.stubs
section like .plt.
Index: mips-tdep.c
===================================================================
RCS file: /big/fsf/rsync/src-cvs/src/gdb/mips-tdep.c,v
retrieving revision 1.379
diff -u -p -r1.379 mips-tdep.c
--- mips-tdep.c 17 Mar 2005 18:07:46 -0000 1.379
+++ mips-tdep.c 27 Apr 2005 14:12:21 -0000
@@ -2091,11 +2091,21 @@ static const struct frame_unwind mips_st
static const struct frame_unwind *
mips_stub_frame_sniffer (struct frame_info *next_frame)
{
+ struct obj_section *s;
CORE_ADDR pc = frame_pc_unwind (next_frame);
+
if (in_plt_section (pc, NULL))
return &mips_stub_frame_unwind;
- else
- return NULL;
+
+ /* Binutils for MIPS puts lazy resolution stubs into .MIPS.stubs. */
+ s = find_pc_section (pc);
+
+ if (s != NULL
+ && strcmp (bfd_get_section_name (s->objfile->obfd, s->the_bfd_section),
+ ".MIPS.stubs") == 0)
+ return &mips_stub_frame_unwind;
+
+ return NULL;
}
static CORE_ADDR
next prev parent reply other threads:[~2005-05-09 3:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 22:39 John Van Horne
2005-04-25 6:22 ` Atsushi Nemoto
2005-04-25 13:05 ` Daniel Jacobowitz
2005-04-27 14:18 ` Daniel Jacobowitz
2005-04-27 16:00 ` Daniel Jacobowitz
2005-04-28 15:16 ` Atsushi Nemoto
2005-05-09 3:16 ` Atsushi Nemoto
2005-05-09 3:36 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 16:36 John Van Horne
2004-12-24 9:32 Atsushi Nemoto
2005-01-04 20:30 ` Andrew Cagney
2005-01-06 10:37 ` Atsushi Nemoto
2005-01-07 1:12 ` 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=20050509033631.GA31464@nevyn.them.org \
--to=drow@false.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jvh@tivo.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