From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] Fix chng-syms.exp for remote stubs
Date: Sun, 29 Feb 2004 02:56:00 -0000 [thread overview]
Message-ID: <20040229025629.GA3182@nevyn.them.org> (raw)
In-Reply-To: <20040228174831.GA16253@nevyn.them.org>
On Sat, Feb 28, 2004 at 12:48:31PM -0500, Daniel Jacobowitz wrote:
> gdb_continue_to_end, used earlier in this file, may set a breakpoint at
> exit. We can't easily delete that breakpoint, because we're testing for
> another breakpoint's behaviour. The easiest fix is to allow the breakpoint
> at exit to count as a pass, since it indicates we didn't stop somewhere
> else or crash.
>
> Also anchor the other match, as Corinna and I noticed earlier.
>
> Will commit in a day or two. Fixes chng-syms.exp on arm-linux using
> gdbserver.
I've committed this patch to HEAD and GDB 6.1, after testing both on
i386-pc-linux-gnu.
> 2004-02-28 Daniel Jacobowitz <drow@mvista.com>
>
> * gdb.base/chng-syms.exp: Anchor exit pattern. Allow
> a breakpoint at exit.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-29 2:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 17:48 Daniel Jacobowitz
2004-02-29 2:56 ` Daniel Jacobowitz [this message]
2004-02-29 3:09 ` Andrew Cagney
2004-02-29 6:50 ` Eli Zaretskii
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=20040229025629.GA3182@nevyn.them.org \
--to=drow@false.org \
--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