From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>,
Andrew Burgess <andrew.burgess@embecosm.com>,
gdb-patches@sourceware.org
Subject: Re: [committed][gdb/testsuite] Don't leak tuiterm.exp spawn override
Date: Wed, 17 Jun 2020 16:55:50 +0200 [thread overview]
Message-ID: <dd7cdcb1-d477-e4b0-3206-6f501b1204ab@suse.de> (raw)
In-Reply-To: <87d060i02k.fsf@tromey.com>
On 6/15/20 9:46 PM, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>
>>> There was a report recently about gdb overrides like this breaking
>>> with a newer dejagnu.
>
> Tom> You're referring to this (
> Tom> https://sourceware.org/pipermail/gdb/2020-June/048689.html ) ?
>
> Yeah.
>
> Tom> Now the idiom is:
> Tom> ...
> Tom> -load_lib tuiterm.exp
> Tom> +tuiterm_env
> Tom> ...
>
> Looks good, thanks.
>
> Tom> I've also tried wrapping the test-case body using the tuiterm_env proc,
> Tom> like this:
> Tom> ...
> Tom> tuiterm_env {
> Tom> ...
> Tom> }
> Tom> ...
> Tom> but ran into curly-braces trouble in gdb.tui/new-layout.exp.
>
> Very unexpected.
That's essentially:
...
$ cat ./test.tcl
#!/usr/bin/tclsh
puts "1: {"
proc do_this { body } {
return [uplevel 1 $body]
}
do_this {
puts "2: {"
}
...
and:
...
$ ./test.tcl
1: {
missing close-brace
while executing
"do_this {"
(file "./test.tcl" line 9)
...
Thanks,
- Tom
next prev parent reply other threads:[~2020-06-17 14:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 16:30 [PATCH 3/3][gdb/testsuite] Warn about leaked global array Tom de Vries
2020-05-22 20:15 ` Tom Tromey
2020-06-02 13:08 ` Tom de Vries
2020-06-02 15:38 ` Andrew Burgess
2020-06-02 15:52 ` Andrew Burgess
2020-06-02 16:31 ` Tom de Vries
2020-06-02 17:01 ` Andrew Burgess
2020-06-02 20:18 ` Andrew Burgess
2020-06-03 8:47 ` Tom de Vries
2020-06-03 9:38 ` Tom de Vries
2020-06-03 10:09 ` Tom de Vries
2020-06-03 10:24 ` Tom de Vries
2020-06-03 12:54 ` Andrew Burgess
2020-06-03 15:35 ` Tom de Vries
2020-06-04 11:16 ` Pedro Alves
2020-06-04 12:29 ` Tom de Vries
2020-06-12 13:11 ` [committed] gdb/testsuite: Prevent globals leaking between test scripts Tom de Vries
2020-06-03 9:49 ` [PATCH 3/3][gdb/testsuite] Warn about leaked global array Pedro Alves
2020-06-04 11:40 ` Tom de Vries
2020-06-05 10:06 ` [PATCH][gdb/testsuite] Don't leak tuiterm.exp spawn override Tom de Vries
2020-06-11 13:55 ` Tom Tromey
2020-06-12 11:36 ` [committed][gdb/testsuite] " Tom de Vries
2020-06-15 19:46 ` Tom Tromey
2020-06-17 14:55 ` Tom de Vries [this message]
2020-06-17 15:28 ` Andreas Schwab
2020-06-11 12:11 ` [committed][gdb/testsuite] Make gdb.base/dbx.exp more robust Tom de Vries
2020-06-11 12:16 ` Pedro Alves
2020-06-11 14:39 ` Simon Marchi
2020-06-11 14:52 ` Tom de Vries
2020-06-11 14:59 ` Simon Marchi
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=dd7cdcb1-d477-e4b0-3206-6f501b1204ab@suse.de \
--to=tdevries@suse.de \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tom@tromey.com \
/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