public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "arjan at linux dot intel.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/14494] New: gdb crashes in bfd_getl16 on debuginfo file
Date: Sat, 18 Aug 2012 13:42:00 -0000 [thread overview]
Message-ID: <bug-14494-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14494
Bug #: 14494
Summary: gdb crashes in bfd_getl16 on debuginfo file
Product: gdb
Version: 7.5
Status: NEW
Severity: normal
Priority: P2
Component: gdb
AssignedTo: unassigned@sourceware.org
ReportedBy: arjan@linux.intel.com
Classification: Unclassified
Created attachment 6590
--> http://sourceware.org/bugzilla/attachment.cgi?id=6590
the libc.so file that causes the crash
gdb -readnow /usr/lib/debug/lib64/libc-2.16.so.debug
gives the following backtrace:
#0 bfd_getl16 (p=0x7fd47abc965b) at libbfd.c:570
#1 0x000000000057333a in read_2_bytes (buf=0x7fd47abc965b <Address
0x7fd47abc965b out of bounds>, abfd=<optimized out>)
at dwarf2read.c:13088
#2 dwarf_parse_macro_header
(opcode_definitions=opcode_definitions@entry=0x7fff1d59ddf0,
abfd=abfd@entry=0x26ed6c0,
mac_ptr=0x7fd47abc965b <Address 0x7fd47abc965b out of bounds>,
offset_size=offset_size@entry=0x7fff1d59dde8,
section_is_gnu=section_is_gnu@entry=1) at dwarf2read.c:17156
#3 0x000000000057c1ac in dwarf_decode_macros (cu=cu@entry=0x27929b0,
offset=5835,
comp_dir=0x7fd47c59d368 <Address 0x7fd47c59d368 out of bounds>,
section_is_gnu=section_is_gnu@entry=1)
at dwarf2read.c:17509
#4 0x0000000000589a81 in read_file_scope (cu=<optimized out>, die=<optimized
out>) at dwarf2read.c:7691
#5 process_die (die=<optimized out>, cu=cu@entry=0x27929b0) at
dwarf2read.c:6872
#6 0x000000000058d7da in process_full_comp_unit
(pretend_language=language_minimal, per_cu=0x2702790) at dwarf2read.c:6680
#7 process_queue () at dwarf2read.c:6250
#8 dw2_do_instantiate_symtab (per_cu=per_cu@entry=0x2702790) at
dwarf2read.c:2177
#9 0x000000000058dd2c in dw2_instantiate_symtab (per_cu=0x2702790) at
dwarf2read.c:2198
#10 0x000000000058e192 in dw2_expand_all_symtabs (objfile=<optimized out>) at
dwarf2read.c:3136
#11 0x0000000000509996 in symbol_file_add_with_addrs_or_offsets
(abfd=<optimized out>, add_flags=6, addrs=addrs@entry=0x0,
flags=<optimized out>, flags@entry=0, parent=parent@entry=0x0,
num_offsets=0, offsets=0x0) at symfile.c:1126
#12 0x0000000000509c4a in symbol_file_add_from_bfd (abfd=<optimized out>,
add_flags=<optimized out>, addrs=addrs@entry=0x0,
flags=flags@entry=0, parent=parent@entry=0x0) at symfile.c:1198
#13 0x0000000000509c91 in symbol_file_add (name=name@entry=0x7fff1d59fdaa
"/usr/lib/debug/lib64/libc-2.16.so.debug",
add_flags=<optimized out>, addrs=addrs@entry=0x0, flags=flags@entry=0) at
symfile.c:1210
#14 0x000000000050a045 in symbol_file_add_main_1 (args=0x7fff1d59fdaa
"/usr/lib/debug/lib64/libc-2.16.so.debug", from_tty=1,
flags=0) at symfile.c:1235
#15 0x000000000052e6cf in catch_command_errors (command=0x50a1a0
<symbol_file_add_main>,
arg=arg@entry=0x7fff1d59fdaa "/usr/lib/debug/lib64/libc-2.16.so.debug",
from_tty=1, mask=mask@entry=6) at exceptions.c:573
#16 0x0000000000530add in captured_main (data=data@entry=0x7fff1d59ea80) at
main.c:899
(the crash happens also on a regular "bt" command of some crashed application,
but this is the easiest testcase)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-08-18 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 13:42 arjan at linux dot intel.com [this message]
2012-08-18 13:44 ` [Bug gdb/14494] " arjan at linux dot intel.com
2012-08-18 14:40 ` arjan at linux dot intel.com
2012-08-18 16:59 ` jan.kratochvil at redhat dot com
2012-08-27 16:43 ` cvs-commit at gcc dot gnu.org
2012-08-27 16:44 ` cvs-commit at gcc dot gnu.org
2012-08-27 16:44 ` cvs-commit at gcc dot gnu.org
2012-08-27 16:46 ` jan.kratochvil at redhat 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-14494-4717@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).