From: Michael Chastain <mec.gnu@mindspring.com>
To: manjo@austin.ibm.com
Cc: gdb@sources.redhat.com
Subject: Re: gdb.gdb/ testcase issues.
Date: Thu, 19 Aug 2004 21:23:00 -0000 [thread overview]
Message-ID: <41251A45.nail58D215HD7@mindspring.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408191014360.21237@lazy>
Hi Manoj,
First thing ... do you have a copyright assignment on file
for gdb?
> 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.
Michael
next prev parent reply other threads:[~2004-08-19 21:23 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 [this message]
2004-08-19 22:16 ` Manoj Iyer
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=41251A45.nail58D215HD7@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb@sources.redhat.com \
--cc=manjo@austin.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).