From: Fernando Nasser <fnasser@redhat.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] gdb.base/finish.exp: Allow finish to stop on call
Date: Wed, 23 May 2001 19:06:00 -0000 [thread overview]
Message-ID: <3B0C6C0C.A81AD343@redhat.com> (raw)
In-Reply-To: <1010524013728.ZM31605@ocotillo.lan>
Kevin Buettner wrote:
>
> On May 23, 8:18pm, Fernando Nasser wrote:
>
> > Your second pattern needs a small improvement though. As we are
> > returning to the middle of that source line, the information printed by
> > GDB will have the address (PC) as well. We must make sure that we test
> > for that so we can differentiate between returning to the beginning of
> > the calling line (wrong) and returning to after where the assembler jump
> > to subroutine was (right). You can test for that without binding to a
> > specific PC value -- there are several examples around.
> >
> > After making this change, and testing that it works, of course, you can
> > commit your patch. Please post the final version for the records.
>
> The patch you refer to has already been committed. (Michael S. approved
> it.)
>
Michael got confused, he can checkin anywhere but can only approve
patches to gdb.trace and gdb.threads (for now, at least). But no big
deal, this is close to an obvious fix.
> I do agree that it is worthwhile to make the pattern more restrictive
> and have just committed the patch below. I've tested it on the IA-64
> machine where I was previously seeing a failure. (It still works as
> expected.)
>
Yes! That is what I meant.
Thank you very much.
> * gdb.base/finish.exp (finish_void): Revise pattern for
> stopping on the call statement to not permit stopping at
> the start of the instructions comprising the call sequence.
>
> Index: testsuite/gdb.base/finish.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/finish.exp,v
> retrieving revision 1.4
> diff -u -p -r1.4 finish.exp
> --- finish.exp 2001/05/22 00:25:27 1.4
> +++ finish.exp 2001/05/24 00:59:25
> @@ -85,7 +85,7 @@ proc finish_void { } {
> -re ".*void_checkpoint.*$gdb_prompt $" {
> pass "finish from void_func"
> }
> - -re ".*call to void_func.*$gdb_prompt $" {
> + -re "0x\[0-9a-fA-F\]+ in main.*call to void_func.*$gdb_prompt $" {
> pass "finish from void_func"
> }
> -re ".*$gdb_prompt $" {
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2001-05-23 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 17:38 Kevin Buettner
2001-05-18 18:24 ` Michael Snyder
2001-05-21 17:27 ` Kevin Buettner
2001-05-23 17:21 ` Fernando Nasser
2001-05-23 18:53 ` Kevin Buettner
2001-05-23 19:06 ` Fernando Nasser [this message]
2001-05-23 19:56 ` Michael Snyder
2001-05-24 6:47 ` Fernando Nasser
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=3B0C6C0C.A81AD343@redhat.com \
--to=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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