From: Andreas Schwab <schwab@suse.de>
To: <Paul_Koning@Dell.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Python 3 support, part 2 (testsuite part)
Date: Wed, 26 Dec 2012 23:48:00 -0000 [thread overview]
Message-ID: <mvmfw2sxtlu.fsf@hawking.suse.de> (raw)
In-Reply-To: <C75A84166056C94F84D238A44AF9F6AD29C3D6@AUSX10MPC103.AMER.DELL.COM> (Paul Koning's message of "Mon, 12 Nov 2012 16:10:46 +0000")
<Paul_Koning@Dell.com> writes:
> diff -u -r1.7 py-finish-breakpoint.exp
> --- gdb/testsuite/gdb.python/py-finish-breakpoint.exp 22 Jun 2012 17:59:33 -0000 1.7
> +++ gdb/testsuite/gdb.python/py-finish-breakpoint.exp 9 Nov 2012 22:26:56 -0000
> @@ -23,6 +23,13 @@
>
> load_lib gdb-python.exp
>
> +if { $gdb_py_is_py24 == 1 } {
Running ../../../gdb/gdb/testsuite/gdb.python/py-finish-breakpoint.exp ...
ERROR: tcl error sourcing ../../../gdb/gdb/testsuite/gdb.python/py-finish-breakpoint.exp.
ERROR: can't read "gdb_py_is_py24": no such variable
while executing
"if { $gdb_py_is_py24 == 1 } {
# Python 2.4, 2.5 do not support the "ValueError as e" syntax used in
# the py-finish-breakpoint.py script.
unt..."
(file "../../../gdb/gdb/testsuite/gdb.python/py-finish-breakpoint.exp" line 26)
invoked from within
"source ../../../gdb/gdb/testsuite/gdb.python/py-finish-breakpoint.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source ../../../gdb/gdb/testsuite/gdb.python/py-finish-breakpoint.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2012-12-26 23:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 16:11 Paul_Koning
2012-11-16 19:32 ` Tom Tromey
2012-11-19 15:34 ` Paul_Koning
2012-12-10 21:09 ` Paul_Koning
2012-12-10 21:13 ` Tom Tromey
2012-12-10 21:22 ` Paul_Koning
2012-12-26 23:48 ` Andreas Schwab [this message]
2013-01-13 8:25 ` Joel Brobecker
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=mvmfw2sxtlu.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=Paul_Koning@Dell.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