From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: asm-source.exp: anchor regexp matching entry point symbol name
Date: Mon, 10 Dec 2001 12:32:00 -0000 [thread overview]
Message-ID: <npsnai24t0.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: Michael Snyder's message of Mon, 10 Dec 2001 10:10:31 -0800
Committed, thanks.
Michael Snyder <msnyder@cygnus.com> writes:
>
> Jim Blandy wrote:
> >
> > 2001-12-08 Jim Blandy <jimb@redhat.com>
> >
> > * gdb.asm/asm-source.exp (info symbol): Anchor the pattern
> > matching the entry point symbol's name at the beginning of the
> > line.
>
> Thanks -- that's what I meant to do.
> Please check it in.
>
> >
> > Index: gdb/testsuite/gdb.asm/asm-source.exp
> > ===================================================================
> > RCS file: /cvs/src/src/gdb/testsuite/gdb.asm/asm-source.exp,v
> > retrieving revision 1.12
> > diff -c -r1.12 asm-source.exp
> > *** gdb/testsuite/gdb.asm/asm-source.exp 2001/12/07 02:50:02 1.12
> > --- gdb/testsuite/gdb.asm/asm-source.exp 2001/12/08 19:49:07
> > ***************
> > *** 122,128 ****
> > -re "info symbol 0x$entry_point\[\r\n\]*" {
> > exp_continue
> > }
> > ! -re "(.*) in section .*$gdb_prompt $" {
> > set entry_symbol $expect_out(1,string)
> > pass "info symbol"
> > }
> > --- 122,131 ----
> > -re "info symbol 0x$entry_point\[\r\n\]*" {
> > exp_continue
> > }
> > ! -re "^(.*) in section .*$gdb_prompt $" {
> > ! # It's important to anchor the pattern above at the beginning
> > ! # of the line. Without that carat, the (.*) may end up
> > ! # matching the empty string.
> > set entry_symbol $expect_out(1,string)
> > pass "info symbol"
> > }
>
prev parent reply other threads:[~2001-12-10 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-08 11:50 Jim Blandy
2001-12-10 10:13 ` Michael Snyder
2001-12-10 12:32 ` Jim Blandy [this message]
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=npsnai24t0.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.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