From: Michael Snyder <msnyder@vmware.com>
To: Michael Snyder <msnyder@vmware.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] gdb_continue_to_breakpoint
Date: Thu, 04 Sep 2008 22:03:00 -0000 [thread overview]
Message-ID: <48C05AF3.1020309@vmware.com> (raw)
In-Reply-To: <20080904213640.GA29721@caradoc.them.org>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
Daniel Jacobowitz wrote:
> On Thu, Sep 04, 2008 at 02:26:17PM -0700, Michael Snyder wrote:
>> Yabbut, this isn't a test of symbol handling, it's
>> a test of continuing to a breakpoint.
>
> True, though we have a lot of things that are tested 'all over' like
> this.
>
>>> For the second part can you just put the .* at
>>> appropriate callers?
>> Sure, if you prefer. So maybe remove the .* but accept
>> the (in|at)?
>
> Yes please. That part seems fine - it's not like nothing else will
> break if we end up unexpectedly without debug info :-).
>
OK, revised and committed as attached.
Thanks
[-- Attachment #2: lib.txt --]
[-- Type: text/plain, Size: 738 bytes --]
2008-09-04 Michael Snyder <msnyder@vmware.com>
* lib/gdb.exp (gdb_continue_to_breakpoint): Accept "in" as well
as "at" (for non-debug functions such as _start).
Index: lib/gdb.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/gdb.exp,v
retrieving revision 1.105
diff -u -p -r1.105 gdb.exp
--- lib/gdb.exp 15 Aug 2008 15:18:34 -0000 1.105
+++ lib/gdb.exp 4 Sep 2008 21:58:38 -0000
@@ -456,7 +456,7 @@ proc gdb_continue_to_breakpoint {name {l
send_gdb "continue\n"
gdb_expect {
- -re "Breakpoint .* at $location_pattern\r\n$gdb_prompt $" {
+ -re "Breakpoint .* (at|in) $location_pattern\r\n$gdb_prompt $" {
pass $full_name
}
-re ".*$gdb_prompt $" {
prev parent reply other threads:[~2008-09-04 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 20:53 Michael Snyder
2008-09-04 21:04 ` Daniel Jacobowitz
2008-09-04 21:27 ` Michael Snyder
2008-09-04 21:37 ` Daniel Jacobowitz
2008-09-04 22:03 ` Michael Snyder [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=48C05AF3.1020309@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
/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