From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: [commit] Regression for gdb.base/stap-probe.exp (and some others) [Re: [patch] Have gdb_breakpoint call pass]
Date: Mon, 15 Oct 2012 19:12:00 -0000 [thread overview]
Message-ID: <20121015191239.GA27906@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22RycAJMTCejrh0sdAvUPNAVr8qHDv2QrHbJi=RCtUKKHQ@mail.gmail.com>
On Mon, 15 Oct 2012 20:49:59 +0200, Doug Evans wrote:
> I gather the issue is that the code is now treating { allow-pending }
> like " allow-pending ", and the test for "allow-pending" (no spaces)
> is now failing.
Surprisingly not, I do not find it too clear:
gdb_breakpoint "$function" { allow-pending }
->
args=<{ allow-pending }>
gdb_breakpoint "$function" {allow-pending}
->
args=<allow-pending>
> Given that gdb_breakpoint is a varargs function, and
> parameters like allow-pending are part of the varargs parameters, it
> seems wrong to pass allow-pending as a list itself (which the braces
> imply), so perhaps we should remove the braces altogether.
> i.e., s/{ allow-pending }/allow-pending/
Checked in that way.
Thanks,
Jan
http://sourceware.org/ml/gdb-cvs/2012-10/msg00056.html
--- src/gdb/testsuite/ChangeLog 2012/10/15 17:35:54 1.3414
+++ src/gdb/testsuite/ChangeLog 2012/10/15 19:11:56 1.3415
@@ -1,3 +1,11 @@
+2012-10-15 Jan Kratochvil <jan.kratochvil@redhat.com>
+ Doug Evans <dje@google.com>
+
+ Fix recent gdb_breakpoint regression.
+ * gdb.java/jmisc.exp: gdb_breakpoint for $function - remove curly
+ braces from the parameter.
+ * gdb.java/jprint.exp: Likewise.
+
2012-10-15 Doug Evans <dje@google.com>
* lib/gdb.exp (runto): Fix call to gdb_breakpoint.
--- src/gdb/testsuite/gdb.java/jmisc.exp 2012/06/22 16:44:15 1.25
+++ src/gdb/testsuite/gdb.java/jmisc.exp 2012/10/15 19:11:56 1.26
@@ -43,8 +43,8 @@
# signature.
runto_main
set function "${testfile}.main(java.lang.String\[\])"
- gdb_breakpoint "$function" { allow-pending }
- gdb_breakpoint "${function}void" { allow-pending }
+ gdb_breakpoint "$function" allow-pending
+ gdb_breakpoint "${function}void" allow-pending
gdb_continue_to_breakpoint $function
gdb_test_multiple "ptype jmisc" "ptype jmisc" {
--- src/gdb/testsuite/gdb.java/jprint.exp 2012/06/22 16:44:15 1.23
+++ src/gdb/testsuite/gdb.java/jprint.exp 2012/10/15 19:11:56 1.24
@@ -43,8 +43,8 @@
# signature.
runto_main
set function "${testfile}.main(java.lang.String\[\])"
- gdb_breakpoint "$function" { allow-pending }
- gdb_breakpoint "${function}void" { allow-pending }
+ gdb_breakpoint "$function" allow-pending
+ gdb_breakpoint "${function}void" allow-pending
gdb_continue_to_breakpoint $function
gdb_test "p jvclass.addprint(4,5,6)" " = 15" "unambiguous static call"
prev parent reply other threads:[~2012-10-15 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 16:49 [patch] Have gdb_breakpoint call pass dje
2012-10-12 7:02 ` Regression for gdb.base/stap-probe.exp (and some others) [Re: [patch] Have gdb_breakpoint call pass] Jan Kratochvil
2012-10-15 13:50 ` Doug Evans
2012-10-15 17:41 ` dje
2012-10-15 18:35 ` Jan Kratochvil
2012-10-15 18:50 ` Doug Evans
2012-10-15 19:12 ` Jan Kratochvil [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=20121015191239.GA27906@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.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