From: Andrew Cagney <cagney@gnu.org>
To: fnf@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix incorrect use of "until" command in gdb.arch/gdb1431
Date: Thu, 26 Feb 2004 21:04:00 -0000 [thread overview]
Message-ID: <403E5F6C.4050001@gnu.org> (raw)
In-Reply-To: <200402192003.08113.fnf@ninemoons.com>
> The gdb.arch/gdb1431 command is using the "until" command incorrectly.
> As currently defined, that command ONLY stops at a point within the
> current frame or upon return from the current frame. You have to use
> the "advance" command to stop at a frame called by the current frame
> or a frame called by a caller of the current frame.
Hmm, "How did it ever work"? :-) I guess so, but keep the 1531.c
specific test file - we've had our fingers burt when trying to use the
one test source file on multiple tests.
Andrew
> 2004-02-19 Fred Fish <fnf@redhat.com>
>
> * gdb.arch/gdb1431.c: Remove.
> * gdb.arch/gdb1431.exp: Reuse test file from PR 1291 and use
> "advance" correctly instead of "until" incorrectly.
>
next prev parent reply other threads:[~2004-02-26 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 3:03 Fred Fish
2004-02-26 21:04 ` Andrew Cagney [this message]
2004-02-26 22:29 ` Fred Fish
2004-02-26 23:01 ` 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=403E5F6C.4050001@gnu.org \
--to=cagney@gnu.org \
--cc=fnf@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