Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: Fernando Nasser <fnasser@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Shorten the maint.exp symbols tests
Date: Wed, 04 Dec 2002 14:20:00 -0000	[thread overview]
Message-ID: <20021204222031.GA1112@nevyn.them.org> (raw)
In-Reply-To: <ro1wump78qj.fsf@jackfruit.Stanford.EDU>

On Wed, Dec 04, 2002 at 01:52:04PM -0800, David Carlton wrote:
> The maint.exp changes in question cause testsuite failures on my
> system for 'maint print symbols' and 'maint print psymbols'.  I've
> played around with it a bit; it seems to me that if I do
> 
> (gdb) maint print symbols symbols_output ./gdb.base/break.c
> 
> (which is what maint.exp does in my situation) then I get an empty
> file symbols_output, whereas if I just do
> 
> (gdb) maint print symbols symbols_output gdb.base/break.c
> 
> then I get the correct symbols_output file.  Here, I'm running GDB
> from within the testsuite directory; I don't use a separate build
> directory when configuring GDB, which might or might not make a
> difference.

Blech!  I'm not sure what to do about this.  Somehow we'd need to
figure out how the file was compiled - is the logic to decide this in
gdb_compile?  Does the compiler clean it up on its own?  Maybe if we
pass an explicit srcdir to gdb_compile we can get consistent results
here.

Or maybe we should make 'maint print symbols symbols_output break.c'
match all files ending in break.c.  That's much less fragile.  What do
you think?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-12-04 22:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 18:58 Daniel Jacobowitz
2002-12-03  7:19 ` Fernando Nasser
2002-12-04 13:52   ` David Carlton
2002-12-04 14:20     ` Daniel Jacobowitz [this message]
2002-12-04 14:47       ` David Carlton
2002-12-05 12:50         ` David Carlton

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=20021204222031.GA1112@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@math.stanford.edu \
    --cc=fnasser@redhat.com \
    --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