From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: gdb@sourceware.cygnus.com, mschalit@pacbell.net
Subject: Re: GDB 5.0 testsuite failures
Date: Sun, 11 Feb 2001 19:19:00 -0000 [thread overview]
Message-ID: <200102120319.TAA20530@bosch.cygnus.com> (raw)
Hi Matthew,
> Thanks for the quick reply. After this, is it proper to
> post a gbd backtrace here and ask for help?
> It's only 11 lines.
Sure, go ahead. The availability of help varies widely from hour to
hour though.
> If that bug doesn't occur when I do the following,
> then I'm safe:
>
> (gdb) file /usr/local/bin/gnomecc
> (gdb) run
> (gdb) bt
Yeah, your gdb ought to be able to backtrace just fine.
> ftp://63.194.213.179:710/pub/Random/gdb.log
Would it be OK with you if I entered this in the public test report
database at http://sources.redhat.com/cgi-bin/gdb.cgi ?
Michael Elizabeth Chastain
<chastain@redhat.com>
"love without fear"
next reply other threads:[~2001-02-11 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 19:19 Michael Elizabeth Chastain [this message]
2001-02-12 0:39 ` Matt Schalit
-- strict thread matches above, loose matches on Subject: below --
2001-02-10 22:38 Michael Elizabeth Chastain
2001-02-11 18:58 ` Matt Schalit
2001-02-10 19:55 Matt Schalit
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=200102120319.TAA20530@bosch.cygnus.com \
--to=chastain@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=mschalit@pacbell.net \
/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