Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: Eli Zaretskii <eliz@gnu.org>,  gdb@sources.redhat.com
Subject: Re: $thread convenience variable
Date: Fri, 03 Feb 2006 13:10:00 -0000	[thread overview]
Message-ID: <200602031610.12398.ghost@cs.msu.su> (raw)
In-Reply-To: <43E35434.4070201@st.com>

On Friday 03 February 2006 16:01, Andrew STUBBS wrote:
> Vladimir Prus wrote:
> > With it, the $thread variable will mean the last thread where we've
> > stopped, as opposed to the current one -- that is, does not change after
> > "thread XXX" command. This might be confusing to users, or might not.
>
> It might be better to do this in cli-script.c in the same way as
> $arg0-$arg9 and $argc. That way it would always be up to date and would
> be read-only.

Is that technically feasible? The $thread variable must be set before the call 
to bpstat_stop_status, otherwise you can't use $thread in breakpoint 
condition. Well, you can, but when evaluating breakpoint condition you'll use 
the old value of $thread, not the number of the thread where we've stopped.

Unless cli-script.c is somehow invoked from handle_inferior_event.

- Volodya


  reply	other threads:[~2006-02-03 13:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-30 20:19 Vladimir Prus
2006-02-03 10:58 ` Eli Zaretskii
2006-02-03 11:10   ` Vladimir Prus
2006-02-03 11:28     ` Eli Zaretskii
2006-02-03 11:59       ` Vladimir Prus
2006-02-03 15:14         ` Eli Zaretskii
2006-02-03 13:04     ` Andrew STUBBS
2006-02-03 13:10       ` Vladimir Prus [this message]
2006-02-03 13:56         ` Andrew STUBBS
2006-02-06 23:52           ` Daniel Jacobowitz
2006-02-06 23:49       ` Daniel Jacobowitz
2006-02-07 10:59         ` Andrew STUBBS
2006-02-07 19:31           ` Daniel Jacobowitz

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=200602031610.12398.ghost@cs.msu.su \
    --to=ghost@cs.msu.su \
    --cc=andrew.stubbs@st.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.redhat.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