This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Variable objects in multi-threaded programs

From: Nick Roberts <nickrob at snap dot net dot nz>
To: Vladimir Prus <vladimir at codesourcery dot com>
Cc: gdb-patches at sources dot redhat dot com
Date: Thu, 24 Jan 2008 20:35:01 +1300
Subject: Re: [PATCH] Variable objects in multi-threaded programs
References: <18328.5277.85018.374650@kahikatea.snap.net.nz> <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

Follow-Ups:
- Re: [PATCH] Variable objects in multi-threaded programs
  - From: Nick Roberts

References:
- [PATCH] Variable objects in multi-threaded programs
  - From: Nick Roberts
- Re: [PATCH] Variable objects in multi-threaded programs
  - From: Vladimir Prus

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]