[Bug gdb/14202] BFD: reopening/tmp/9501_._navl_3.0.0.32-9657_amd64_plugins_ad.plg: No such file ordirectory

["tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

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.