From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu
Cc: ezannoni@redhat.com, fnasser@redhat.com, gdb@sources.redhat.com,
jimb@redhat.com
Subject: Re: [rfc] plans for linespec.c
Date: Thu, 09 Jan 2003 16:09:00 -0000 [thread overview]
Message-ID: <200301091609.h09G96e01574@duracef.shout.net> (raw)
David Carlton writes:
> Fair enough. It's something I should get around to doing eventually
> for other reasons; maybe your nudging will move it up some.
Right. I have to allocate my time between 'do stuff with tangible
gdb benefits' and 'do stuff that improves my own infrastructure'.
Sometimes I feel like I'm just infrastructuring my test bed too much.
> Speaking of which, I had the thought that maybe we could do unit tests
> of some of the innards of GDB by writing separate test programs that
> we link with -lgdb. Something to think about.
That is a provocative idea. I know Jim B wrote one symbol table test
that jumped through a bunch of hoops with the C source code in order
to populate the symbol table in a way that tickled a lookup bug.
On the gloomy side, the test suite can already spot problems faster than
I can file bug reports, and the bug reports are piling up faster than
people can fix them.
Michael C
next reply other threads:[~2003-01-09 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 16:09 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 4:24 Michael Elizabeth Chastain
2003-01-09 6:01 ` David Carlton
2003-01-09 9:45 ` Joel Brobecker
2003-01-08 0:12 Michael Elizabeth Chastain
2003-01-08 23:22 ` David Carlton
2003-01-07 22:22 David Carlton
2003-01-08 14:25 ` Elena Zannoni
2003-01-08 22:48 ` 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=200301091609.h09G96e01574@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@math.stanford.edu \
--cc=ezannoni@redhat.com \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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