public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/16201] internal error on a cygwin program linked against a DLL with no .data section
Date: Thu, 21 Nov 2013 21:30:00 -0000 [thread overview]
Message-ID: <bug-16201-4717-35NB0S83TT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16201-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16201
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
CC| |tromey at redhat dot com
--- Comment #2 from Tom Tromey <tromey at redhat dot com> ---
I tried it with "gdb icudt49.dll" using git master gdb,
and it worked fine for me.
Does this test cause your gdb to fail?
Given the location of the error, I would expect so.
If your gdb fails but mine does not, then the bug has been fixed.
If your gdb does not fail then I'd like a self-contained
test case. I don't have a cygwin box on which to try this;
but it ought to be host-independent anyhow, since it occurs
in symbol reading...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-11-21 21:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 19:29 [Bug gdb/16201] New: " smaximov at yahoo dot com
2013-11-21 20:37 ` [Bug gdb/16201] " smaximov at yahoo dot com
2013-11-21 21:09 ` smaximov at yahoo dot com
2013-11-21 21:30 ` tromey at redhat dot com [this message]
2013-11-21 21:36 ` smaximov at yahoo dot com
2013-11-21 21:39 ` tromey at redhat dot com
2013-11-21 21:54 ` smaximov at yahoo dot com
2013-11-21 22:01 ` tromey at redhat dot com
2013-11-21 22:04 ` smaximov at yahoo dot com
2013-11-22 15:58 ` tromey at redhat dot com
2013-11-22 23:48 ` smaximov at yahoo dot com
2013-11-23 17:23 ` keiths at redhat dot com
2013-11-25 18:30 ` smaximov at yahoo dot com
2013-11-25 21:33 ` tromey at redhat dot com
2013-11-25 21:56 ` tromey at redhat dot com
2013-11-26 0:21 ` smaximov at yahoo dot com
2013-11-26 2:20 ` muller at sourceware dot org
2013-11-26 3:13 ` smaximov at yahoo dot com
2013-11-27 0:04 ` smaximov at yahoo dot com
2013-12-02 11:33 ` asmwarrior at gmail dot com
2013-12-21 0:49 ` smaximov at yahoo dot com
2013-12-21 1:02 ` asmwarrior at gmail dot com
2023-12-09 12:46 ` ssbssa at sourceware dot org
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-16201-4717-35NB0S83TT@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).