From: Daniel Jacobowitz <drow@false.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: jvh@tivo.com, gdb@sources.redhat.com
Subject: Re: gdb 6.x 'next' does not work on mips-linux/mipsel-linux
Date: Mon, 25 Apr 2005 13:05:00 -0000 [thread overview]
Message-ID: <20050425130124.GA7316@nevyn.them.org> (raw)
In-Reply-To: <20050425.152157.34482010.nemoto@toshiba-tops.co.jp>
On Mon, Apr 25, 2005 at 03:21:57PM +0900, Atsushi Nemoto wrote:
> >>>>> On Fri, 22 Apr 2005 15:39:06 -0700, "John Van Horne" <jvh@tivo.com> said:
> jvh> I just posted a note on PR 1716 about my experience with this
> jvh> problem. Basically, "next" on a dynamically linked library
> jvh> function fails for me using gdb 6.2.1, 6.3 and 6.3.50.20050420. I
> jvh> saw the previous posts in this thread that made it sound as
> jvh> though this was fixed in the 20050104 snapshot. However I
> jvh> couldn't find that snapshot, and the latest failed for me.
>
> I tried 6.3.50.20050329 and 6.3.50.20050424 and got same errors.
> It seems broken again before 20050329.
>
> FYI, my ugly hack for gdb 6.3 seems work for current snapshot too.
> (http://sources.redhat.com/ml/gdb/2004-12/msg00118.html)
Drat. I will look into this.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-04-25 13:01 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 [this message]
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
-- 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=20050425130124.GA7316@nevyn.them.org \
--to=drow@false.org \
--cc=anemo@mba.ocn.ne.jp \
--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