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: Tue, 12 Jun 2012 19:49:00 -0000 [thread overview] Message-ID: <bug-14202-4717-XJI9SbXNcQ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14202-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14202 Tom Tromey <tromey at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at redhat dot com --- Comment #2 from Tom Tromey <tromey at redhat dot com> 2012-06-12 19:49:04 UTC --- (In reply to comment #0) > gdb console in netbeans 7.1.2 shows the following message: > > =library-loaded,id="/tmp/9501_._navl_3.0.0.32-9657_amd64_plugins_ad.plg" This means gdb saw your program load this shared library. > 15-stack-list-frames > BFD: reopening /tmp/9501_._navl_3.0.0.32-9657_amd64_plugins_ad.plg: No such > file or directory At this point, gdb tries to reopen the library (not sure why, but there can be various reasons); but at this point it has been deleted. > 2. appears gdb thinks there should be a /tmp file, and there are no /tmp files > created in this debugging session. Apparently not the case. gdb tries to lazily load debuginfo sections. This could cause this problem -- but you say the file is stripped, so I would guess it is something else. There's sort of a known problem here where BFD can close file descriptors and reopen them, which is not always safe in scenarios like this. One thing that might help is a stack trace at the point where gdb emits this message. I'm not entirely sure what to do in this area. Changing BFD not to close fds would be nice, but won't work on all hosts (or perhaps, I have heard, not even all filesystems). Eagerly mapping debuginfo sections might help (if that is the bug here), but that hurts memory use always to support a relatively obscure scenario (deleting a .so after dlopening it). -- 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-12 19:49 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 [this message] 2012-06-13 14:02 ` tbuckley at isc8 dot com 2012-06-13 19:18 ` tromey at redhat dot com 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-XJI9SbXNcQ@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: linkBe 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).