From: Manoj Iyer <manjo@austin.ibm.com>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb.gdb/ testcase issues.
Date: Thu, 19 Aug 2004 22:16:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0408191637370.21237@lazy> (raw)
In-Reply-To: <41251A45.nail58D215HD7@mindspring.com>
> First thing ... do you have a copyright assignment on file
> for gdb?
Will get back to you on that.
>
> > Is there any real reason for setting breakpoints on such fucntions?
> > If not I will be happy to provide a patch that fixes this problem.
>
> I don't know any reason, but I haven't looked yet.
>
> The counter-question is: why are you running gdb.gdb tests on a stripped
> gdb executable? Other parts of selftest.exp depend on stepping one
> source line at a time, which won't work with a stripped executable.
>
The reason is, the GDB that is shipped in a distro is stripped, and I used
the --tool_exec= option to use this GDB that is installed in /usr/bin. So
my understanding so far is that the testcases under gdb.gdb are to be used
only for a GDB that is build fresh from sources and not that is installed
on the system. If that is the case then they need to be modified in such a
way that they report that "the testcase does not support stripped gdb --
unsupported" or something of that nature. Is that ok?
--
Manoj Iyer
next prev parent reply other threads:[~2004-08-19 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 18:10 Manoj Iyer
2004-08-19 21:23 ` Michael Chastain
2004-08-19 22:16 ` Manoj Iyer [this message]
2004-08-20 8:51 ` Michael Chastain
2004-08-25 5:03 ` [RFC] GDB testsuite patch Manoj Iyer
2004-08-25 12:49 ` Daniel Jacobowitz
2004-08-25 13:48 ` Michael Chastain
2004-08-25 13:44 ` Michael Chastain
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=Pine.LNX.4.58.0408191637370.21237@lazy \
--to=manjo@austin.ibm.com \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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