From: Elena Zannoni <ezannoni@redhat.com>
To: Stephane Carrez <stcarrez@nerim.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Fix testsuite/gdb.base/break.exp when test compiled with -DPROTOTYPES
Date: Mon, 24 Feb 2003 21:34:00 -0000 [thread overview]
Message-ID: <15962.37096.719113.658720@localhost.redhat.com> (raw)
In-Reply-To: <3E5A8C4F.7020000@nerim.fr>
Stephane Carrez writes:
> Hi!
>
> In the gdb.base/break.c test, the function marker4() is defined at line 46 when
> the test is compiled with -DPROTOTYPES and at line 51 otherwise. The break.exp
> test only check for line 51.
>
> This patch adds the missing regexp for marker4 at line 46.
> (tested with make check for m6811-elf; break.exp passes completely)
>
> Can you approve it?
>
Could this be fixed by adding a comment to the lines in question,
use gdb_get_line_number, and use that in the test?
elena
> Thanks,
> Stephane
>
> 2003-02-24 Stephane Carrez <stcarrez@nerim.fr>
>
> * gdb.base/break.exp: marker4() is defined at line 46 when compiled
> with -DPROTOTYPES.
> Index: gdb.base/break.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/break.exp,v
> retrieving revision 1.14
> diff -u -p -r1.14 break.exp
> --- gdb.base/break.exp 16 Jan 2003 01:56:15 -0000 1.14
> +++ gdb.base/break.exp 24 Feb 2003 21:13:24 -0000
> @@ -907,11 +907,16 @@ if ![target_info exists use_gdb_stub] {
> # as if it were in the middle of a line rather than at the beginning.
>
> send_gdb "continue\n"
> +# marker4() is defined at line 46 when compiled with -DPROTOTYPES
> +# and at line 51 otherwise.
> gdb_expect {
> -re "Breakpoint $decimal, marker4 \\(d=177601976\\) at .*$srcfile:51\[\r\n\]+51\[\t \]+void marker4.*" {
> pass "run until breakpoint set at small function, optimized file"
> }
> -re "Breakpoint $decimal, $hex in marker4 \\(d=177601976\\) at .*$srcfile:51\[\r\n\]+51\[\t \]+void marker4.*" {
> + pass "run until breakpoint set at small function, optimized file"
> + }
> + -re "Breakpoint $decimal, marker4 \\(d=177601976\\) at .*$srcfile:46\[\r\n\]+46\[\t \]+void marker4.*" {
> pass "run until breakpoint set at small function, optimized file"
> }
> -re ".*$gdb_prompt " {
next prev parent reply other threads:[~2003-02-24 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 21:19 Stephane Carrez
2003-02-24 21:34 ` Elena Zannoni [this message]
2003-02-24 21:46 ` Stephane Carrez
2003-02-24 23:34 ` Jason Molenda
2003-04-04 20:09 ` Stephane Carrez
2003-04-04 20:41 Michael Elizabeth Chastain
2003-04-04 21:31 ` Stephane Carrez
2003-04-04 22:29 ` Daniel Jacobowitz
2003-04-05 10:46 ` Stephane Carrez
2003-04-05 13:20 ` 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=15962.37096.719113.658720@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=stcarrez@nerim.fr \
/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