From: Brad Aisa <baisa@colorado.edu>
To: gdb@sourceware.org
Subject: GDB fails from Kdbg
Date: Wed, 12 Oct 2005 17:05:00 -0000 [thread overview]
Message-ID: <200510121105.16110.baisa@colorado.edu> (raw)
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.
AN EXECUTABLE FILE IS AVAILABLE TO REPRODUCE THE ISSUE -- I didn't
attach it because many mail lists reject attached documents.
Environment:
Linux Fedora Core 4, 2.6.12-1398
i686
GDB 6.3
KDbg 1.3 or 2.0 (doesn't matter)
Issue:
Open Kdbg; select an executable to debug.
Error message: "'gdb' exited unexpectedly"
This issue happens for a binary compiled with gcc 4.0.1 as well as one
compiled with gcc 3.3.
I have contacted the Kdbg folks, and they have investigated and assure
the issue is with GDB. Other KDE users are experiencing this issue.
--
Brad Aisa <baisa at colorado dot edu>
Professional Research Assistant
Department of Psychology
University of Colorado - Boulder
next reply other threads:[~2005-10-12 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 17:05 Brad Aisa [this message]
2005-10-12 17:41 ` Daniel Jacobowitz
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=200510121105.16110.baisa@colorado.edu \
--to=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).