public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13242] MinGW-GDB crash in coff_symtab_read when running child program
Date: Sun, 31 Dec 2023 12:56:21 +0000 [thread overview]
Message-ID: <bug-13242-4717-SA157KNbaE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13242-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13242
Hannes Domani <ssbssa at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ssbssa at sourceware dot org
--- Comment #4 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Tom Tromey from comment #3)
> Sorry, nobody got to downloading the bad .exe when it
> was still around. If this is still an issue, I think just
> the .exe would be enough to reproduce the bug.
The file was apparently moved, I found it at this new location:
http://dukeworld.duke4.net/eduke32/synthesis/old/2011/20110928-2047/eduke32_win32_20110928-2047.zip
But I can't reproduce any crash, not even with the compiled gdb he provided.
Maybe I would need a full Duke Nukem 3D copy to reproduce the issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-12-31 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 6:13 [Bug gdb/13242] New: " Hendricks266 at gmail dot com
2011-10-01 17:00 ` [Bug gdb/13242] " Hendricks266 at gmail dot com
2011-12-21 21:15 ` Hendricks266 at gmail dot com
2011-12-21 21:50 ` Hendricks266 at gmail dot com
2012-01-19 23:56 ` Hendricks266 at gmail dot com
2012-01-20 0:00 ` Hendricks266 at gmail dot com
2022-12-01 21:31 ` tromey at sourceware dot org
2023-12-31 12:56 ` ssbssa at sourceware dot org [this message]
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=bug-13242-4717-SA157KNbaE@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).