From: Faheem Mitha <faheem@email.unc.edu>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: setfault calling functions within gdb
Date: Tue, 10 Sep 2002 20:12:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0209102305320.13388-100000@Chrestomanci> (raw)
In-Reply-To: <vt2ofb6xsf5.fsf@zenia.red-bean.com>
On 10 Sep 2002, Jim Blandy wrote:
>
> I don't see anything obviously wrong with what you're doing (although
> someone is certain to pop up and correct me). Could you file this as
> a bug report at http://sources.redhat.com/gdb/bugs/, so it won't get
> lost?
I've sent it to the Debian bug tracking system, against gdb. Is that Ok?
One reason for doing so is because it is a version of gdb that is from
cvs, so is presumably unique to Debian. Also, I prefer the Debian
interface. :-) I suppose I can send a copy to
http://sources.redhat.com/gdb/bugs/ if you think that is necessary.
Faheem.
next prev parent reply other threads:[~2002-09-11 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 20:58 Faheem Mitha
2002-09-09 23:49 ` Jim Blandy
2002-09-10 20:12 ` Faheem Mitha [this message]
2002-09-10 6:27 ` Daniel Jacobowitz
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.44.0209102305320.13388-100000@Chrestomanci \
--to=faheem@email.unc.edu \
--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