Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Srinath Avadhanula <srinathava@gmail.com>
To: Srinath Avadhanula <srinathava@gmail.com>, gdb@sourceware.org
Subject: Re: A question about data-directory
Date: Mon, 30 Aug 2010 23:22:00 -0000	[thread overview]
Message-ID: <AANLkTimiO+2FBft1tNzfZ=axZ6yTZfzV4rq3P0+9GqAG@mail.gmail.com> (raw)
In-Reply-To: <20100830230035.GA5311@caradoc.them.org>

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.
----------%<------------

It does say that "gdb will look for a file named ..." rather than it
being only available on Python's search path.

Is the doc wrong/out-dated?

Regards,
Srinath


  reply	other threads:[~2010-08-30 23:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 22:46 Srinath Avadhanula
2010-08-30 23:00 ` Daniel Jacobowitz
2010-08-30 23:22   ` Srinath Avadhanula [this message]
2010-08-31 13:08     ` Daniel Jacobowitz

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='AANLkTimiO+2FBft1tNzfZ=axZ6yTZfzV4rq3P0+9GqAG@mail.gmail.com' \
    --to=srinathava@gmail.com \
    --cc=gdb@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