From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com, fnasser@redhat.com
Subject: Re: [RFA/testsuite] Handle MIPS in step-test.exp
Date: Tue, 22 Oct 2002 07:25:00 -0000 [thread overview]
Message-ID: <20021022142537.GA16933@nevyn.them.org> (raw)
In-Reply-To: <3DB55E72.3060700@redhat.com>
On Tue, Oct 22, 2002 at 10:19:30AM -0400, Andrew Cagney wrote:
> >The MIPS PIC calling conventions have a $gp register which needs to be
> >reloaded after function calls, so they need the same treatment IA-64 and PA
> >do in step-test. I also needed to finish stepping past one call before
> >looking for the next or the test showed a bogus failure.
>
> Is this a straight GDB bug?
It's a straight testsuite bug. The test is full of assumptions about
when nexti will move to the next source line.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-10-22 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 19:02 Daniel Jacobowitz
2002-10-22 7:19 ` Andrew Cagney
2002-10-22 7:25 ` Daniel Jacobowitz [this message]
2002-11-27 10:55 ` Andrew Cagney
2002-12-03 7:18 ` Fernando Nasser
2002-12-03 7:55 ` Andrew Cagney
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=20021022142537.GA16933@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.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