From: Michael Chastain <mec.gnu@mindspring.com>
To: gdb@sources.redhat.com, esp5@pge.com
Subject: Re: debugger 6.2.1 misfeatures
Date: Sat, 11 Sep 2004 01:46:00 -0000 [thread overview]
Message-ID: <4142590A.nailCR31XGTUA@mindspring.com> (raw)
In-Reply-To: <20040910235746.GA11043@mdssdev05>
Sounds like a bug to me.
Generally for a bug, we need:
the gdb version
the host operating system version
the target operating system version (if it's not the same as the host)
a typescript of the whole gdb session showing the bug
(use the 'script' command)
some info about the inferior program:
what language it's written in
the exact compiler name and compiler version that it was built with
Then if somebody picks up the bug, they're likely to come back with
more questions. The point at this stage is not to identify the bug,
but just to throw enough information over the fence so that the
gdb engineer can *reproduce* the bug.
If it worked with a previous version of gdb, that's good to know.
It's really great if you can supply a small test program
(source + binary) that demonstrates the bug.
And some bug reports are successful and get fixed, and some aren't
and don't.
Michael Chastain
next prev parent reply other threads:[~2004-09-11 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 0:05 Edward Peschko
2004-09-11 1:46 ` Michael Chastain [this message]
2004-09-11 9:59 ` Monika Chaddha
2004-09-11 15:52 ` Michael Chastain
2004-09-13 7:01 ` Monika Chaddha
2004-09-11 16:26 ` Joel Brobecker
2004-09-15 6:37 ` Joel Brobecker
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=4142590A.nailCR31XGTUA@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=esp5@pge.com \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).