This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: A question about data-directory
On Mon, Aug 30, 2010 at 07:21:59PM -0400, Srinath Avadhanula wrote:
> Hi Daniel,
>
> On Mon, Aug 30, 2010 at 7:00 PM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
> > On Mon, Aug 30, 2010 at 06:46:49PM -0400, Srinath Avadhanula wrote:
> >> I was expecting the output from the auto-load script to say 'getting
> >> here' before getting back to the prompt. If I place test-gdb.py in the
> >> same directory as the executable (i.e. at /tmp/test/test-gdb.py) then
> >> I do get a line saying 'getting here'.
> >
> > IIUC, that's what's supposed to happen right now. ?The 'python'
> > directory in datadir is added to the Python search path, but gdb.py
> > files are searched for next to the object file.
> >
>
> That seems to flatly contradict what is mentioned in the doc:
>
> ----------%<------------
> Finally, if this file does not exist, then gdb will look for a file
> named data-directory/python/auto-load/real-name, where data-directory
> is gdb's data directory (available via show data-directory, see Data
> Files), and real-name is the object file's real name, as described
> above.
> ----------%<------------
I think this is a different search option - and you're misreading
REAL-NAME. The real name is going to be $DATADIR/tmp/test/test.
Also, the docs appear to be wrong, by stracing GDB:
open("../gdb", O_RDONLY) = 7
open("/space/fsf/x86-64/commit-gdb/gdb/gdb-gdb.py", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/lib/debug/space/fsf/x86-64/commit-gdb/gdb/gdb-gdb.py",
O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/share/gdb/auto-load/space/fsf/x86-64/commit-gdb/gdb/gdb-gdb.py",
O_RDONLY) = -1 ENOENT (No such file or directory)
--
Daniel Jacobowitz
CodeSourcery