From: "Jim Blandy" <jimb@red-bean.com>
To: "M R Swami Reddy" <MR.Swami.Reddy@nsc.com>
Cc: gdb@sourceware.org
Subject: Re: gdb testsuite
Date: Wed, 30 Jan 2008 17:56:00 -0000 [thread overview]
Message-ID: <8f2776cb0801300956q276d3cdahcc6fe3855983b8c@mail.gmail.com> (raw)
In-Reply-To: <47A073FD.9060103@nsc.com>
It's not obvious to me where the -lm comes from. gdb/testsuite/lib
contains a number of files that are also involved in running the
tests; in particular, gdb_compile is defined in
gdb/testsuite/lib/gdb.exp.
One unfortunate characteristic of the GDB test suite is that, even if
GDB is horribly broken, many tests will still pass. You can't have
much confidence that things are basically working with 356 failures.
You should look through gdb.log and work through a bunch of them to
get a feel for the state of things.
If you're going to do any significant amount of work with the test
suite, I would recommend investing a little time in learning the Tcl
language. It's built on some very simple concepts, and knowing how
those actually work, instead of guessing based on the resemblance
between Tcl and more familiar languages, will save confusion in the
future. I think there are tutorials on-line somewhere.
next prev parent reply other threads:[~2008-01-30 17:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 10:14 M R Swami Reddy
2008-01-25 18:16 ` Jim Blandy
2008-01-28 5:07 ` M R Swami Reddy
2008-01-28 18:51 ` Jim Blandy
2008-01-29 6:07 ` M R Swami Reddy
2008-01-29 20:22 ` Jim Blandy
2008-01-30 12:56 ` M R Swami Reddy
2008-01-30 17:56 ` Jim Blandy [this message]
2008-01-30 19:53 ` Thiago Jung Bauermann
2008-01-30 23:54 ` Jim Blandy
2008-01-31 17:33 ` Thiago Jung Bauermann
2008-02-01 11:45 ` M R Swami Reddy
-- strict thread matches above, loose matches on Subject: below --
2006-07-25 12:09 qinwei
1999-05-20 4:34 GDB testsuite Rajesh Maddali
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=8f2776cb0801300956q276d3cdahcc6fe3855983b8c@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=MR.Swami.Reddy@nsc.com \
--cc=gdb@sourceware.org \
/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