From: Doug Evans <dje@google.com>
To: pmuldoon@redhat.com
Cc: Robert Lupton the Good <rhl@astro.princeton.edu>, gdb@sourceware.org
Subject: Re: Problem writing python tests without installing
Date: Sun, 20 Nov 2011 09:20:00 -0000 [thread overview]
Message-ID: <CADPb22TBeh98SN4VAiauVGuVichEJk=MXO_YUBak3OdfS0FhBg@mail.gmail.com> (raw)
In-Reply-To: <m3sjlwkm61.fsf@redhat.com>
On Thu, Nov 10, 2011 at 7:54 AM, Phil Muldoon <pmuldoon@redhat.com> wrote:
> Robert Lupton the Good <rhl@astro.princeton.edu> writes:
>
>> When running the testsuite, the python files that are sourced are apparently e.g.
>> gdb/testsuite/../data-directory/python/gdb/printing.py
>> rather than
>> gdb/python/lib/gdb/printing.py
>> although the binary is as expected gdb/gdb
>
> Right, but you don't have to do 'make install' to get data-directory.
>
>>
>> The files appear to be installed by "make install". This is another
>> manifestation of the problem that you cannot apparently work on the
>> gdb python code without first installing it (away from it's cvs home
>> -- but that can be faked with a link...)
>
> I work with Python every day and I don't have this issue. The files are
> correctly sourced from ../data-dictionary.
>
> I could not find the gdb.printing test in my output, but this works fine:
>
> python
>>Sending "import gdb.command.prompt" to gdb
> Looking to match ""[\r\n]*()[\r\n]+(\(gdb\) | *>)$""
> Message is "prompt substitution readline - import gdb.command.prompt"
> board_info host exists name
>
> FWIW GDB is spawned in the test as:
>
> Spawning /home/pmuldoon/bugs/setex/obj/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/pmuldoon/bugs/setex/obj/gdb/testsuite/../data-directory
>
>> Is there a proper way to work around this?
>
> There's not enough information on your install/setup to diagnose the
> issue. How did you configure the build?
Yeah, I suspect the problem is either an absence of "-data-directory
..." when starting gdb, or not doing a "make" after editing a .py file
(*1).
[And if you add new .py files, remember to mention them in
data-directory/Makefile.in]
---
(*1) Since .py files aren't "compiled" having to do a "make" may be
unexpected, but it's ultimately easier to stage them in
$build/data-directory rather than trying to fetch them from the the
source tree.
prev parent reply other threads:[~2011-11-20 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 13:15 Robert Lupton the Good
2011-11-10 15:55 ` Phil Muldoon
2011-11-20 9:20 ` Doug Evans [this message]
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='CADPb22TBeh98SN4VAiauVGuVichEJk=MXO_YUBak3OdfS0FhBg@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=rhl@astro.princeton.edu \
/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).