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/14202] BFD: reopening /tmp/9501_._navl_3.0.0.32-9657_amd64_plugins_ad.plg: No such file or directory
Date: Wed, 13 Jun 2012 19:18:00 -0000 [thread overview]
Message-ID: <bug-14202-4717-38ObAfVR2q@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14202-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14202
--- Comment #4 from Tom Tromey <tromey at redhat dot com> 2012-06-13 19:17:49 UTC ---
(In reply to comment #3)
> Why does gdb keep track of a library that has been stripped and has no
> information? Seems like it should ignore the plugins and when the breakpoint is
> hit it will not have the problem of "No such file or directory"
At least in my case it is reading .eh_frame:
#0 _bfd_default_error_handler (fmt=0x16cb019 "reopening %B: %s\n")
at ../../archer/bfd/bfd.c:587
#1 0x0000000000994707 in bfd_cache_lookup_worker (abfd=0x2137680,
flag=CACHE_NO_SEEK) at ../../archer/bfd/cache.c:227
#2 0x00000000009947bc in cache_bseek (abfd=0x2137680, offset=1512, whence=0)
at ../../archer/bfd/cache.c:244
#3 0x0000000000993d35 in bfd_seek (abfd=0x2137680, position=1512,
direction=0) at ../../archer/bfd/bfdio.c:327
#4 0x0000000000768f54 in dwarf2_read_section (objfile=0x2507ae0, info=
0x250fe50) at ../../archer/gdb/dwarf2read.c:1748
#5 0x0000000000769371 in dwarf2_get_section_info (objfile=0x2507ae0,
sect=DWARF2_EH_FRAME, sectp=0x2510080, bufp=0x2510070, sizep=0x2510078)
at ../../archer/gdb/dwarf2read.c:1855
#6 0x00000000007aaa38 in dwarf2_build_frame_info (objfile=0x2507ae0)
at ../../archer/gdb/dwarf2-frame.c:2266
#7 0x00000000007a96ea in dwarf2_frame_find_fde (pc=0x7fffffffda80,
out_offset=0x0) at ../../archer/gdb/dwarf2-frame.c:1749
#8 0x00000000007a8dd0 in dwarf2_frame_sniffer (self=0xf4f1e0, this_frame=
0x1fe4fd0, this_cache=0x1fe4fe8) at ../../archer/gdb/dwarf2-frame.c:1382
#9 0x0000000000817ca5 in frame_unwind_find_by_frame (this_frame=0x1fe4fd0,
this_cache=0x1fe4fe8) at ../../archer/gdb/frame-unwind.c:112
One idea might be to change how the BFD caching is done:
on "ok" systems, don't ever close the file descriptors, and on
other systems, eagerly map all sections.
--
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 prev parent reply other threads:[~2012-06-13 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 20:59 [Bug gdb/14202] New: " tbuckley at isc8 dot com
2012-06-05 21:02 ` [Bug gdb/14202] " tbuckley at isc8 dot com
2012-06-12 19:49 ` tromey at redhat dot com
2012-06-13 14:02 ` tbuckley at isc8 dot com
2012-06-13 19:18 ` tromey at redhat dot com [this message]
2012-06-18 15:33 ` tbuckley at isc8 dot com
2012-10-02 9:33 ` srhaque at theiet 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-14202-4717-38ObAfVR2q@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).