From: Carlo Wood <carlo@alinoe.com>
To: Jim Blandy <jimb@zwingli.cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: [carlo@alinoe.com: Re: RFC c++ debugging thread]
Date: Wed, 04 Jul 2001 05:17:00 -0000 [thread overview]
Message-ID: <20010704141715.C17190@alinoe.com> (raw)
In-Reply-To: <npu20tq3po.fsf@zwingli.cygnus.com>
On Tue, Jul 03, 2001 at 01:15:15PM -0500, Jim Blandy wrote:
> Carlo Wood <carlo@alinoe.com> writes:
> > Sent originally to the wrong list.
> > Note I am not subbed to gdb@sources.redhat.com.
>
> Thanks!
>
> Unfortunately, this still isn't really enough information. Think of
> it this way: in order for us to fix a bug, we need step-by-step
> instructions which allow us to reproduce the bug ourselves, on our own
> machine.
It wasn't meant to be :). I already sent this before you requested
more info. I'll try to fix up some test cases when I run into these
problems next time.
--
Carlo Wood <carlo@alinoe.com>
prev parent reply other threads:[~2001-07-04 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 20:37 Carlo Wood
2001-07-03 11:14 ` Jim Blandy
2001-07-04 5:17 ` Carlo Wood [this message]
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=20010704141715.C17190@alinoe.com \
--to=carlo@alinoe.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@zwingli.cygnus.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