From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>,
Simon Marchi <simon.marchi@polymtl.ca>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] native-gdbserver: Clear isremote flag in board info
Date: Mon, 11 Apr 2016 21:29:00 -0000 [thread overview]
Message-ID: <570C171F.7040603@redhat.com> (raw)
In-Reply-To: <570BF79F.2070409@ericsson.com>
On 04/11/2016 08:14 PM, Simon Marchi wrote:
> On 16-04-11 02:40 PM, Pedro Alves wrote:
>> On 04/06/2016 04:15 AM, Simon Marchi wrote:
>> OOC, don't we need the "global" declarations as
>> in native-extended-gdbserver.exp?
>
> Apparently not, since it works :)
>
:-)
> I'm not familiar enough with TCL to know that. Are we executing in the body
> of a procedure at this point? This file is sourced from some proc in DejaGnu,
> so I'd say yes, but this example may suggest otherwise.
Hmm, that's probably search_and_load_file, which does
"uplevel #0 source ...", meaning top-level global variables are visible
in the sourced file.
>> You're probably already thinking of doing this, but I'll state it
>> explicitly anyway: it'd be nice to move this isremote frobbing to
>> a shared .exp file, so that boards that need it can just
>> source the file.
>
> I wasn't, but it's a good idea. isremote is also handled in an unintuitive way,
> since the testsuite only checks if it's defined. So when you set isremote to 0,
> it's still considered as "true".
Hmm, that sounds like a bug. If that were generally true, then
native-gdbserver.exp's isremote hacks in ${board}_spawn / ${board}_exec
wouldn't work? Where are you seeing that?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-04-11 21:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 3:15 Simon Marchi
2016-04-06 3:15 ` [PATCH 3/4] Fix detach.exp remote check Simon Marchi
2016-04-11 18:16 ` Pedro Alves
2016-05-02 17:11 ` Simon Marchi
2016-04-06 3:15 ` [PATCH 2/4] Fix annota-input-while-running.exp " Simon Marchi
2016-04-11 18:03 ` Pedro Alves
2016-05-02 17:07 ` Simon Marchi
2016-04-06 3:15 ` [PATCH 4/4] Fix solib-display.exp " Simon Marchi
2016-04-11 18:27 ` Pedro Alves
2016-04-11 19:26 ` Simon Marchi
2016-04-11 21:32 ` Pedro Alves
2016-04-11 21:38 ` Pedro Alves
2016-05-02 18:20 ` Simon Marchi
2016-05-02 18:28 ` Pedro Alves
2016-05-02 19:52 ` Simon Marchi
2016-05-03 23:19 ` Pedro Alves
2016-04-11 18:40 ` [PATCH 1/4] native-gdbserver: Clear isremote flag in board info Pedro Alves
2016-04-11 19:14 ` Simon Marchi
2016-04-11 21:29 ` Pedro Alves [this message]
2016-04-11 23:14 ` 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=570C171F.7040603@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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).