Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: Extra diagnostic for tests
Date: Sat, 16 Sep 2006 11:19:00 -0000	[thread overview]
Message-ID: <eegmjq$taq$1@sea.gmane.org> (raw)
In-Reply-To: <200609131352.16082.vladimir@codesourcery.com>

Vladimir Prus wrote:

> 
> Hi,
> at the moment, the dejagnu tests use PATH to find the gdb binary, and
> don't report which gdb binary is used. As result, when running runtest
> manually on one test, one can test with different gdb from the one used by
> 'make check'.
> 
> The attached patch makes gdb print to log file the location of gdb, and
> also makes sure invocation parameters are always printed to log file.
> While we're on it, the 'serialport' parameter to 'target' command is also
> reported.

So, what's opinion on this patch, after all?

I think the part about better reporting 'target remote' seen no objections,
OK to commit that?

Speaking of gdb PATH, I've noticed that the very last line of dejagnu output
contains the full path to gdb -- apparently I used 'Ctrl-C' too much.

Anyway, I think getting this information into log file is still desirable,
and it makes sure that .log file is sufficient to reproduce a test
failures -- console output might be no longer handy.

- Volodya




  parent reply	other threads:[~2006-09-16 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13  9:52 Vladimir Prus
2006-09-13 10:20 ` Mark Kettenis
2006-09-13 12:24   ` Daniel Jacobowitz
2006-09-13 17:58   ` Michael Snyder
2006-09-16 11:19 ` Vladimir Prus [this message]
2006-09-16 14:20   ` Daniel Jacobowitz
2006-09-23 16:55   ` Mark Kettenis

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='eegmjq$taq$1@sea.gmane.org' \
    --to=ghost@cs.msu.su \
    --cc=gdb-patches@sources.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