Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Variable objects in multi-threaded programs
Date: Thu, 24 Jan 2008 06:36:00 -0000	[thread overview]
Message-ID: <fn9bk1$s9m$1@ger.gmane.org> (raw)
In-Reply-To: <18328.5277.85018.374650@kahikatea.snap.net.nz>

Nick Roberts wrote:

> 
> Currently GDB thinks variable objects have gone out of scope if the thread
> changes.  

This is indeed a major problem.

> This patch corrects that. 

I'm somewhat concerned that this patch makes gdb traverse stacks of all
threads -- it can take quite some time. Would a better solution be
to store thread id inside varobj?

- Volodya



  reply	other threads:[~2008-01-24  6:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24  4:32 Nick Roberts
2008-01-24  6:36 ` Vladimir Prus [this message]
2008-01-24 12:41   ` Nick Roberts
2008-01-24 22:24     ` Nick Roberts
2008-01-29 17:43       ` Vladimir Prus
2008-01-30  1:49         ` Nick Roberts
2008-01-30  7:35           ` Vladimir Prus
     [not found]             ` <18336.11753.55351.293036@kahikatea.snap.net.nz>
2008-01-30  8:51               ` Vladimir Prus

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='fn9bk1$s9m$1@ger.gmane.org' \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@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