From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "kettenis@gnu.org" <kettenis@gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"markus.t.metzger@gmail.com" <markus.t.metzger@gmail.com>
Subject: RE: [PATCH 11/16] test, btrace: add branch trace tests
Date: Fri, 01 Jun 2012 11:37:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B2307A9F989@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20120530204346.GI20633@host2.jankratochvil.net>
[-- Attachment #1.1: Type: text/plain, Size: 2691 bytes --]
> -----Original Message-----
> From: Jan Kratochvil [mailto:jan.kratochvil@redhat.com]
> Sent: Wednesday, May 30, 2012 10:44 PM
Thanks for your review!
> > *.log
> > *.sum
> > +
> > +gdb/testsuite/gdb.btrace/list.x
>
> This is excessive.
Removed.
[...]
> > +++ b/gdb/testsuite/gdb.btrace/dec.c
> > @@ -0,0 +1,4 @@
>
> Missing copyright header.
Fixed.
> > +++ b/gdb/testsuite/gdb.btrace/list.s
>
> It should end with .S as it is used in GDB. It should have i386 in its name
> as it
> is x86-specific file.
I renamed it to x86-list.S. It is used for i386 and for x86_64.
[...]
> > +++ b/gdb/testsuite/gdb.btrace/list_function.c
> > @@ -0,0 +1,12 @@
>
> Missing copyright header.
Fixed.
[...]
> > +gdb_reinitialize_dir $srcdir/$subdir
> > +gdb_load $binfile
>
> Why not to use prepare_for_testing here?
Prepare_for_testing uses gcc for linking which pulls in the startup object.
I need more control over what gets linked since I want to be able to rely
on the exact addresses in the final executable.
I used it in list_function.exp, though. Thanks for the hint.
[...]
> > + runto main
>
> Rather always check for 'runto' error codes, it sometimes happens and the
> rest of testfile does not recover well in such case.
Fixed.
> > +
> > + gdb_test_multiple "btrace enable" "check btrace support" {
> > + -re "You can't do that when your target is.*" {
>
> Missing termination:
> -re "You can't do that when your target is.*\r\n$gdb_prompt $" {
>
> As otherwise it will be racy, the leftover prompt can be read in by next
> gdb_test.
Fixed.
> > + unsupported "target does not support btrace"
> > + set skip 1
>
> Here should be:
> xfail "check btrace support"
Fixed.
> > + }
> > + -re "Couldn't enable branch tracing.*Operation not supported"
> > + {
>
> Again.
Fixed.
> > + unsupported "target does not support btrace"
> > + set skip 1
>
> Here should be:
> xfail "check btrace support"
Fixed.
> > + }
>
> > + -re "$gdb_prompt $" {}
>
> One may disagree but I think this block should contain:
> pass "check btrace support"
I added it.
> > + }
> > + gdb_exit
> > + remote_file build delete $testfile
> > +
> > + return $skip
> > +}
> > +
> > +proc btrace_reset_trace {} {
> > + gdb_test_no_output "btr disable"
> > + gdb_test_no_output "btr enable"
> > +
> > + gdb_test "btr list" "No trace." "reset btrace"
>
> For real correctness either
> gdb_test "btr list" "No trace\\." "reset btrace"
> or:
> gdb_test "btr list" {No trace\.} "reset btrace"
Changed to "No trace\.". "No trace\\." wouldn't compile.
Thanks,
Markus.
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 417 bytes --]
--------------------------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
next prev parent reply other threads:[~2012-06-01 11:37 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 11:23 [PATCH 00/16] branch tracing support (resend) markus.t.metzger
2012-05-23 11:24 ` [PATCH 10/16] btrace, config: enable btrace for 32bit and 64bit linux native markus.t.metzger
2012-05-23 11:24 ` [PATCH 06/16] configure: add check for perf_event header markus.t.metzger
2012-05-30 20:43 ` Jan Kratochvil
2012-05-31 15:34 ` Metzger, Markus T
2012-06-22 20:40 ` Tom Tromey
2012-06-25 8:50 ` Metzger, Markus T
2012-05-23 11:24 ` [PATCH 02/16] source: add flags to print_source_lines () markus.t.metzger
2012-05-30 20:41 ` Jan Kratochvil
2012-05-31 15:34 ` Metzger, Markus T
2012-06-22 20:08 ` Tom Tromey
2012-06-25 8:50 ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 15/16] gdbserver, btrace: add generic btrace support markus.t.metzger
2012-05-23 11:25 ` [PATCH 16/16] gdbserver, linux, btrace: add btrace support for linux-low markus.t.metzger
2012-05-23 11:25 ` [PATCH 13/16] xml, btrace: define btrace xml document style markus.t.metzger
2012-05-30 20:44 ` Jan Kratochvil
2012-06-01 8:39 ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 01/16] disas: add precise instructions flag markus.t.metzger
2012-05-23 11:25 ` [PATCH 03/16] source, disasm: optionally prefix source lines with filename markus.t.metzger
2012-05-30 20:41 ` Jan Kratochvil
2012-05-23 11:25 ` [PATCH 14/16] remote, btrace: add branch trace remote ops markus.t.metzger
2012-05-30 20:44 ` Jan Kratochvil
2012-06-01 8:49 ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 08/16] linux, btrace: perf_event based branch tracing markus.t.metzger
2012-05-30 20:43 ` Jan Kratochvil
2012-05-31 15:34 ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 04/16] thread, btrace: add generic branch trace support markus.t.metzger
2012-05-30 20:42 ` Jan Kratochvil
2012-05-31 15:33 ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 05/16] cli, btrace: add btrace cli markus.t.metzger
2012-05-30 20:42 ` Jan Kratochvil
2012-05-31 15:33 ` Metzger, Markus T
2012-06-01 18:42 ` Jan Kratochvil
2012-06-05 9:56 ` Metzger, Markus T
2012-05-23 11:25 ` [PATCH 11/16] test, btrace: add branch trace tests markus.t.metzger
2012-05-30 20:44 ` Jan Kratochvil
2012-06-01 11:37 ` Metzger, Markus T [this message]
2012-05-23 11:25 ` [PATCH 09/16] btrace, linux: add linux native btrace target ops markus.t.metzger
2012-05-30 20:43 ` Jan Kratochvil
2012-05-31 15:34 ` Metzger, Markus T
2012-05-23 11:26 ` [PATCH 12/16] test, btrace: more branch tracing tests markus.t.metzger
2012-05-23 11:26 ` [PATCH 07/16] configure: autoreconf markus.t.metzger
2012-06-22 20:44 ` Tom Tromey
2012-06-25 8:50 ` Metzger, Markus T
2012-05-25 19:18 ` [PATCH 00/16] branch tracing support (resend) Pedro Alves
2012-05-29 14:31 ` Metzger, Markus T
2012-05-30 14:49 ` Pedro Alves
2012-05-30 15:51 ` Metzger, Markus T
2012-05-30 17:56 ` Pedro Alves
2012-05-31 17:11 ` Metzger, Markus T
2012-06-04 6:46 ` Metzger, Markus T
2012-06-12 11:32 ` Metzger, Markus T
2012-06-12 12:09 ` Jan Kratochvil
2012-06-12 12:23 ` Pedro Alves
2012-06-12 12:25 ` Jan Kratochvil
2012-06-12 13:38 ` Metzger, Markus T
2012-05-30 20:41 ` Jan Kratochvil
2012-05-31 15:33 ` Metzger, Markus T
2012-06-22 20:31 ` Tom Tromey
2012-06-25 8:50 ` Metzger, Markus T
2012-07-02 8:29 ` Metzger, Markus T
-- strict thread matches above, loose matches on Subject: below --
2012-05-10 15:15 [PATCH 00/16] branch tracing support markus.t.metzger
2012-05-10 15:17 ` [PATCH 11/16] test, btrace: add branch trace tests markus.t.metzger
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=A78C989F6D9628469189715575E55B2307A9F989@IRSMSX102.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=kettenis@gnu.org \
--cc=markus.t.metzger@gmail.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