From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA/testsuite: test break "marker2"
Date: Fri, 10 May 2002 12:59:00 -0000 [thread overview]
Message-ID: <15580.9846.576737.468732@localhost.redhat.com> (raw)
In-Reply-To: <20020510194918.GA3893@nevyn.them.org>
Daniel Jacobowitz writes:
> Elena pointed out that this doesn't seem to be in the testsuite anywhere.
> I'm considering writing unit tests for some of the linespec code... but
> until then, I'll just keep adding breakpoint tests. Is this OK? Should
> pass everywhere.
>
Can you add a comment about testing decode_line_1 code?
My turn to recommend this for approval to MichaelC. :-)
Thanks
Elena
> --
> Daniel Jacobowitz Carnegie Mellon University
> MontaVista Software Debian GNU/Linux Developer
>
> 2002-05-10 Daniel Jacobowitz <drow@mvista.com>
>
> * gdb.base/break.exp: Check 'break "marker2"'.
>
> Index: testsuite/gdb.base/break.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/break.exp,v
> retrieving revision 1.11
> diff -u -p -r1.11 break.exp
> --- testsuite/gdb.base/break.exp 7 Jan 2002 19:21:27 -0000 1.11
> +++ testsuite/gdb.base/break.exp 10 May 2002 19:38:45 -0000
> @@ -84,6 +84,13 @@ gdb_test "break main" \
> "breakpoint function"
>
> #
> +# test break at quoted function
> +#
> +gdb_test "break \"marker2\"" \
> + "Breakpoint.*at.* file .*$srcfile, line.*" \
> + "breakpoint quoted function"
> +
> +#
> # test break at function in file
> #
> gdb_test "break $srcfile:factorial" \
> @@ -150,6 +157,7 @@ if {$hp_aCC_compiler} {
> gdb_test "info break" \
> "Num Type\[ \]+Disp Enb Address\[ \]+What.*
> \[0-9\]+\[\t \]+breakpoint keep y.* in main at .*$srcfile:$main_line.*
> +\[0-9\]+\[\t \]+breakpoint keep y.* in marker2 at .*$srcfile:4\[49\].*
> \[0-9\]+\[\t \]+breakpoint keep y.* in factorial$proto at .*$srcfile:96.*
> \[0-9\]+\[\t \]+breakpoint keep y.* in main at .*$srcfile:79.*
> \[0-9\]+\[\t \]+breakpoint keep y.* in main at .*$srcfile:79.*
> @@ -208,6 +216,11 @@ for {set i 6} {$i >= 1} {incr i -1} {
> "run until file:function($i) breakpoint"
> }
>
> +#
> +# Run until the breakpoint set at a quoted function
> +#
> +gdb_test continue "Continuing\\..*Breakpoint \[0-9\]+, (0x\[0-9a-f\]+ in )?marker2 \\(a=43\\) at .*$srcfile:4\[49\].*" \
> + "run until quoted breakpoint"
> #
> # run until the file:function breakpoint at a line number in a file
> #
next prev parent reply other threads:[~2002-05-10 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 12:49 Daniel Jacobowitz
2002-05-10 12:59 ` Elena Zannoni [this message]
2002-05-12 9:43 Michael Elizabeth Chastain
2002-05-12 18:18 ` Daniel Jacobowitz
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=15580.9846.576737.468732@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=drow@mvista.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