From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite: break-entry.exp: convert entry point for ppc64
Date: Mon, 08 Nov 2010 18:08:00 -0000 [thread overview]
Message-ID: <20101108180719.GA22604@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <1286462667-14653-1-git-send-email-emachado@linux.vnet.ibm.com>
On Thu, 07 Oct 2010 16:44:27 +0200, Edjunior Barbosa Machado wrote:
> Thanks Jan for the feedback.
> Sending the updated patch with the changes you suggested.
Checked-in, sorry for the delay.
Regards,
Jan
http://sourceware.org/ml/gdb-cvs/2010-11/msg00040.html
--- src/gdb/testsuite/ChangeLog 2010/11/05 17:07:35 1.2501
+++ src/gdb/testsuite/ChangeLog 2010/11/08 18:05:55 1.2502
@@ -1,3 +1,9 @@
+2010-11-08 Edjunior Machado <emachado@br.ibm.com>
+ Luis Machado <luisgpm@br.ibm.com>
+
+ * gdb.base/break-entry.exp: convert entry point for
+ ppc64 and expect leading `.' on ppc64's symbols
+
2010-11-05 Doug Evans <dje@google.com>
* gdb.base/help.exp: Update expected output.
--- src/gdb/testsuite/gdb.base/break-entry.exp 2010/04/04 22:12:14 1.1
+++ src/gdb/testsuite/gdb.base/break-entry.exp 2010/11/08 18:05:56 1.2
@@ -34,10 +34,20 @@
return
}
+if {[istarget powerpc64-*] && [is_lp64_target]} {
+ set test "convert entry point"
+ gdb_test_multiple "p *(void(*)(void) *) $entry" $test {
+ -re " =( \\(\[^0-9\]*\\))? (0x\[0-9a-f\]+)( <.*)?\r\n$gdb_prompt $" {
+ set entry $expect_out(2,string)
+ pass $test
+ }
+ }
+}
+
if ![runto "*$entry"] {
return
}
gdb_test {p/x $pc} " = $entry"
gdb_breakpoint "main"
-gdb_continue_to_breakpoint "main" "main.*"
+gdb_continue_to_breakpoint "main" "\\.?main.*"
prev parent reply other threads:[~2010-11-08 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 1:08 emachado
2010-10-05 21:30 ` Jan Kratochvil
2010-10-07 14:44 ` Edjunior Barbosa Machado
2010-10-20 16:49 ` Edjunior Barbosa Machado
2010-11-08 18:08 ` 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=20101108180719.GA22604@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=emachado@linux.vnet.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).