From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: dje@google.com
Cc: gdb-patches@sourceware.org
Subject: Re: Regression for gdb.base/stap-probe.exp (and some others) [Re: [patch] Have gdb_breakpoint call pass]
Date: Mon, 15 Oct 2012 18:35:00 -0000 [thread overview]
Message-ID: <20121015183521.GA26690@host2.jankratochvil.net> (raw)
In-Reply-To: <20604.19144.405313.95372@ruffy2.mtv.corp.google.com>
Hi Doug,
On Mon, 15 Oct 2012 19:41:28 +0200, dje@google.com wrote:
> This patch fixes stap-probe.exp on the Fedora box I tested on.
Yes, it does.
> I didn't test jmisc.exp but it is likely the same issue.
No, it is not.
I guess you agree, I will check it in. With '{ allow-pending }' the function
gets passed "{ allow-pending }" while with '{allow-pending}' it gets passed
"allow-pending". tcl-8.5.12-3.fc18.x86_64
Thanks,
Jan
gdb/testsuite/
2012-10-15 Jan Kratochvil <jan.kratochvil@redhat.com>
Fix recent gdb_breakpoint regression.
* gdb.java/jmisc.exp: gdb_breakpoint for $function - remove spaces from
curly bracketed parameter.
* gdb.java/jprint.exp: Likewise.
diff --git a/gdb/testsuite/gdb.java/jmisc.exp b/gdb/testsuite/gdb.java/jmisc.exp
index 7215861..64ae559 100644
--- a/gdb/testsuite/gdb.java/jmisc.exp
+++ b/gdb/testsuite/gdb.java/jmisc.exp
@@ -43,8 +43,8 @@ if [set_lang_java] then {
# 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" {
diff --git a/gdb/testsuite/gdb.java/jprint.exp b/gdb/testsuite/gdb.java/jprint.exp
index b2d5d31..ac5c55c 100644
--- a/gdb/testsuite/gdb.java/jprint.exp
+++ b/gdb/testsuite/gdb.java/jprint.exp
@@ -43,8 +43,8 @@ if [set_lang_java] then {
# 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"
next prev parent reply other threads:[~2012-10-15 18:35 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 [this message]
2012-10-15 18:50 ` Doug Evans
2012-10-15 19:12 ` [commit] " Jan Kratochvil
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=20121015183521.GA26690@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