Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: fnasser@redhat.com, jimb@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [Jim Blandy <jimb@redhat.com>] RFA: Add tests for lookup_symbol_aux bug
Date: Sat, 21 Dec 2002 21:14:00 -0000	[thread overview]
Message-ID: <ro1wum2k7la.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <200212210659.gBL6xZJ31187@duracef.shout.net>

On Sat, 21 Dec 2002 00:59:35 -0600, Michael Elizabeth Chastain <mec@shout.net> said:

> It feels a little strange to have a test which will PASS almost all the
> time, even if gdb is broken.

For what it's worth, this test has already caught an unrelated bug, so
it's having surprising benefits.  I think probably the test suite
doesn't pound on the partial symbol table as much as it could, so even
narrowly targeted partial symbol tests like this one are useful.

> (For instance, we could add some maint commands to gdb to force
> specific algorithmic paths in the symbol table reader so that test
> scripts can exercise them).

That sounds like an interesting idea.  I do think that unit tests are
useful, and unfortunately some parts of the symbol table (especially
partial symbols) are buried a bit too deep in GDB's innards to be able
to easily do unit testing on via the test suite.  Maybe maint commands
would help with that.

It would take some thinking to do well, though...

David Carlton
carlton@math.stanford.edu


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20 23:11 Michael Elizabeth Chastain
2002-12-21 20:14 ` Jim Blandy
2002-12-21 21:14 ` David Carlton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-21 21:27 Michael Elizabeth Chastain
2002-12-20 10:54 Jim Blandy
2002-12-20 11:52 ` David Carlton
2002-12-21 18:07   ` Jim Blandy

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=ro1wum2k7la.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=mec@shout.net \
    /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