From: Tom Tromey <tromey@redhat.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [rfa][testsuite] Consolidade Python test functions in lib/gdb.exp.
Date: Mon, 20 Apr 2009 17:13:00 -0000 [thread overview]
Message-ID: <m3ocur45ax.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1240154454.19777.39.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Sun\, 19 Apr 2009 12\:20\:54 -0300")
>>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
Thiago> This is a cleanup on the testcases in gdb.python. Currently,
Thiago> they define the same test functions in each .exp. I put them
Thiago> in lib/gdb.exp instead.
It looks like the GDB style is to put specific support functions into
a new file, e.g., "mi-support.exp". So perhaps we should add
"python-support.exp"... WDYT?
Thiago> +# Return 1 if Python scripting is supported in GDB, 0 if not.
Thiago> +proc python_supported { } {
Thiago> + global gdb_prompt
I think this proc should do the test only once per runtest invocation,
and just return a cached result in subsequent calls.
Otherwise this looks reasonable to me.
Tom
next prev parent reply other threads:[~2009-04-20 17:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 15:21 Thiago Jung Bauermann
2009-04-20 17:13 ` Tom Tromey [this message]
2009-04-20 17:23 ` Daniel Jacobowitz
2009-05-18 4:38 ` Thiago Jung Bauermann
2009-05-18 18:11 ` Eli Zaretskii
2009-05-19 14:50 ` Thiago Jung Bauermann
2009-05-19 14:59 ` Daniel Jacobowitz
2009-05-19 19:22 ` Eli Zaretskii
2009-05-19 22:21 ` Thiago Jung Bauermann
2009-05-20 3:11 ` Eli Zaretskii
2009-05-20 3:26 ` Thiago Jung Bauermann
2009-05-20 3:39 ` Daniel Jacobowitz
2009-05-20 13:18 ` Thiago Jung Bauermann
2009-05-20 14:59 ` Daniel Jacobowitz
2009-05-20 15:10 ` Thiago Jung Bauermann
2009-05-20 17:22 ` Eli Zaretskii
2009-05-20 19:39 ` Thiago Jung Bauermann
2009-05-20 20:00 ` Eli Zaretskii
2009-05-20 20:49 ` Thiago Jung Bauermann
2009-05-20 23:11 ` Joel Brobecker
2009-05-31 22:26 ` Thiago Jung Bauermann
2009-05-31 22:37 ` Thiago Jung Bauermann
2009-06-04 18:03 ` Tom Tromey
2009-05-28 0:43 ` Tom Tromey
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=m3ocur45ax.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@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