From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Variable objects in multi-threaded programs
Date: Thu, 24 Jan 2008 12:41:00 -0000 [thread overview]
Message-ID: <18328.16293.286454.235065@kahikatea.snap.net.nz> (raw)
In-Reply-To: <fn9bk1$s9m$1@ger.gmane.org>
> 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?
Yes I think it would. As an element of struct varobj_root?
Perhaps this should also included as a field in the output of -var-create, the
frontend could organise the display of watch expressions by thread. If we use
the GDB thread id, this would be consistent with infrun.c
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-01-24 7:35 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
2008-01-24 12:41 ` Nick Roberts [this message]
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=18328.16293.286454.235065@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@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