Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Stan Shebs'" <stan@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: RE: [PATCH] $thread convenience variable
Date: Mon, 14 Jun 2010 09:14:00 -0000	[thread overview]
Message-ID: <000f01cb0ba1$fe745c70$fb5d1550$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <4C158675.9090001@codesourcery.com>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Stan Shebs
> Envoyé : Monday, June 14, 2010 3:32 AM
> À : gdb-patches@sourceware.org
> Objet : [PATCH] $thread convenience variable
> 
> This little patch adds a periodically-requested convenience variable
> whose value is the current thread.  It's handy in scripts and
> conditionals, since the GDB-assigned thread id is unpredictable.
> 
> Although the original request was for "$thread", it might be better to
> make it "$_thread" instead, so as not to interfere with possible use in
> existing scripts.  But I'll only change it if I get enough votes in
> favor. :-)

  By analogy with:
 _exitcode
 _siginfo
and
 _tlb 
internal variables defined so far,
I would vote in favor of '$_thread'.

  The only other internal variables I found
are 'bpnum', 'tpnum' and a whole bunch of 'trace_.*' variables.


Pierre Muller
Pascal language support maintainer for GDB




  parent reply	other threads:[~2010-06-14  9:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14  1:31 Stan Shebs
2010-06-14  3:00 ` Eli Zaretskii
2010-06-14  9:14 ` Pierre Muller [this message]
2010-06-14 18:36 ` Tom Tromey
2010-06-18 17:46   ` Stan Shebs
2010-06-18 17:58     ` Pedro Alves

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='000f01cb0ba1$fe745c70$fb5d1550$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=stan@codesourcery.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