From: Brad Aisa <baisa@colorado.edu>
To: gdb@sources.redhat.com
Subject: Re: Status of kdbg bug submission
Date: Thu, 06 Oct 2005 17:44:00 -0000 [thread overview]
Message-ID: <200510061144.10006.baisa@colorado.edu> (raw)
In-Reply-To: <20051006012006.GA21221@nevyn.them.org>
Well, I filled out the form on the gnu site, and it seemed to post
successfully, and told me i'd get some kind of email at some point.
Should I try again? Do I somehow need to be logged in as some kind of
user to send a bug report?
On Wednesday 05 October 2005 07:20 pm, Daniel Jacobowitz wrote:
> On Wed, Oct 05, 2005 at 03:52:48PM -0600, Brad Aisa wrote:
> > I get an error msg "gdb exited unexpectedly" when starting kdbg.
> > I have submitted a bug report to the gdb bug base, and was
> > wondering when I would receive confirmation? I sumitted on Mon
> > 10/03/05.
> >
> > In brief, the context and issue:
> >
> > Linux FC4
> > GDB6.3
> > Kdbg 1.3 or 2.0 (doesn't matter which)
> >
> > Load an executable, the program responds, "GDB exited
> > unexpectedly."
> >
> > The author of KDBG has assured that the issue has been
> > investigated, and lies with gdb, not kdbg.
> >
> > I have a sample executable that can reproduce the issue.
>
> Bugs are responded to, of course, when a volunteer has time.
> However, in this case, I have seen no record of your bug report;
> where did you submit it?
--
Brad Aisa <baisa at colorado dot edu>
Professional Research Assistant
Department of Psychology
University of Colorado - Boulder
next prev parent reply other threads:[~2005-10-06 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 21:54 Brad Aisa
2005-10-06 1:20 ` Daniel Jacobowitz
2005-10-06 17:44 ` Brad Aisa [this message]
2005-10-06 17:52 ` Daniel Jacobowitz
2005-10-06 21:06 ` Joel Brobecker
2005-10-06 21:17 ` Daniel Jacobowitz
2005-10-06 21:49 ` 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=200510061144.10006.baisa@colorado.edu \
--to=baisa@colorado.edu \
--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).