Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4 v3] Documentation and testsuite changes
Date: Fri, 27 Apr 2012 19:58:00 -0000	[thread overview]
Message-ID: <87haw52bzf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3bomjujpm.fsf@redhat.com> (Sergio Durigan Junior's message of	"Mon, 23 Apr 2012 01:59:33 -0300")

>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:

Sergio> +# Run the tests.  We run the tests two different ways: once with a
Sergio> +# plain probe, and once with a probe that has an associated semaphore.
Sergio> +# This returns -1 on failure to compile or start, 0 otherwise.
Sergio> +proc stap_test {{arg ""}} {
[...]
Sergio> +proc stap_test_no_debuginfo {{ arg "" }} {
Sergio> +    global testfile hex
Sergio> +
Sergio> +    if {[prepare_for_testing ${testfile}.exp ${testfile} ${testfile}.c \
[...]

I think it would be preferable if each different set of tests used a
different name for the built executable.  This sort of thing makes it
simpler to debug failing tests.  Also I think it is a newly agreed-upon
convention.

Sergio> diff --git a/gdb/testsuite/gdb.trace/stap-trace.exp b/gdb/testsuite/gdb.trace/stap-trace.exp
[...]
Sergio> +proc compile_stap_bin {{ arg "" }} {
[...]
Sergio> +    if { [gdb_compile "$srcdir/$subdir/$srcfile" $binfile \
Sergio> +	    executable [concat $arg debug nowarnings]] != "" } {

Same here.

Tom


  reply	other threads:[~2012-04-27 19:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23  4:57 [PATCH 0/4 v3] Add support for static and SystemTap probes Sergio Durigan Junior
2012-04-23  4:59 ` [PATCH 2/4 v3] Implement " Sergio Durigan Junior
2012-04-27 19:43   ` Tom Tromey
2012-04-27 20:58     ` Sergio Durigan Junior
2012-04-23  4:59 ` [PATCH 3/4 v3] Use longjmp and exception probes when available Sergio Durigan Junior
2012-04-27 19:47   ` Tom Tromey
2012-04-27 20:58     ` Sergio Durigan Junior
2012-04-23  4:59 ` [PATCH 1/4 v3] Refactor internal variable mechanism Sergio Durigan Junior
2012-04-27 15:40   ` Tom Tromey
2012-04-27 20:57     ` Sergio Durigan Junior
2012-04-23  6:35 ` [PATCH 4/4 v3] Documentation and testsuite changes Sergio Durigan Junior
2012-04-27 19:58   ` Tom Tromey [this message]
2012-04-27 20:32     ` Tom Tromey
2012-04-27 20:57       ` Sergio Durigan Junior
2012-04-28  1:55       ` Sergio Durigan Junior
2012-04-28 23:30 ` Regression for gdb.trace/backtrace.exp [Re: [PATCH 0/4 v3] Add support for static and SystemTap probes] Jan Kratochvil
2012-04-29  6:29   ` Sergio Durigan Junior
2012-04-29 12:59     ` Jan Kratochvil
2012-04-29 18:03       ` Sergio Durigan Junior

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=87haw52bzf.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.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