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/12866] gdb fail to load elf compiled by ARM RVCT3.1
Date: Thu, 31 Oct 2013 20:55:00 -0000 [thread overview]
Message-ID: <bug-12866-4717-NPddWhSQ7i@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12866-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=12866
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |tromey at redhat dot com
Resolution|INVALID |---
--- Comment #7 from Tom Tromey <tromey at redhat dot com> ---
(In reply to Will Newton from comment #6)
> The DWARF in this file is corrupt and causes a loop in the structure of the
> debug information, causing gdb to allocate increasing amounts of memory.
> It's not clear that it can be avoided with this type of corruption.
Could you post your analysis and say what exactly is wrong
with the DWARF?
I think it is valuable to try to harden gdb against this kind
of error.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-31 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 14:15 [Bug gdb/12866] New: " lkn0371 at 163 dot com
2011-06-09 14:20 ` [Bug gdb/12866] " lkn0371 at 163 dot com
2011-06-10 12:25 ` qiyao at gcc dot gnu.org
2011-06-13 2:39 ` lkn0371 at 163 dot com
2011-06-13 2:41 ` lkn0371 at 163 dot com
2011-06-13 4:58 ` lkn0371 at 163 dot com
2011-06-15 14:30 ` lkn0371 at 163 dot com
2011-06-16 5:45 ` [Bug gdb/12866] gdb " lkn0371 at 163 dot com
2013-10-30 19:38 ` will.newton at gmail dot com
2013-10-31 20:55 ` tromey at redhat dot com [this message]
2013-11-06 15:15 ` cvs-commit at gcc dot gnu.org
2013-11-06 15:17 ` will.newton at gmail dot com
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-12866-4717-NPddWhSQ7i@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).