From: Daniel Jacobowitz <drow@false.org>
To: Brad Aisa <baisa@colorado.edu>
Cc: gdb@sourceware.org
Subject: Re: GDB fails from Kdbg
Date: Wed, 12 Oct 2005 17:41:00 -0000 [thread overview]
Message-ID: <20051012174112.GA26260@nevyn.them.org> (raw)
In-Reply-To: <200510121105.16110.baisa@colorado.edu>
On Wed, Oct 12, 2005 at 11:05:16AM -0600, Brad Aisa wrote:
> Hi Everyone,
>
> I tried on two different occasions to enter this bug on the gdb bug
> entry page, and both times the process failed -- I submitted, but no
> PR was generated. So I'm posting the details here.
As I told you, it was filed but the outgoing mail was lost. It's PR
2019. The mail problem has been fixed. However, the PR has absolutely
no information useful for anyone to reproduce anything. Neither does
this message. Presumably "the kdbg folks" know something more specific
about what the bug is; why don't you include _that_ information?
How about when loading your executable directly into GDB? Does that
work?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-10-12 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 17:05 Brad Aisa
2005-10-12 17:41 ` Daniel Jacobowitz [this message]
2005-10-12 18:29 ` Brad Aisa
2005-10-12 18:53 ` Daniel Jacobowitz
2005-10-12 19:58 ` Brad Aisa
2005-10-12 20:01 ` Daniel Jacobowitz
2005-10-12 22:03 ` Brad Aisa
2005-10-13 3:18 ` 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=20051012174112.GA26260@nevyn.them.org \
--to=drow@false.org \
--cc=baisa@colorado.edu \
--cc=gdb@sourceware.org \
/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).