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] |
"It would be nice." There was some discussion in that general vein back around 2002-3, connected with dwarf2 computed locations; http://sourceware.org/ml/gdb-patches/2002-07/msg00124.html alludes to the idea for example."Stan" == Stan Shebs <stan@codesourcery.com> writes:
Stan> This patch solves a couple intertwined problems relating to Stan> tracepoint collection of C++ classes with static fields. First, Stan> it adds recognition of variables (including static fields) whose Stan> location expressions indicate that they have been optimized out.
As ax-gdb grows I am starting to wonder whether we could unify it with
eval.c somehow.
Hmm, I'll check it out - I wonder it's flattened out, static field iteration doesn't seem to recurse as one might expect.Stan> Second, to collect an instance of a class with static fields, we Stan> need to issue more bytecodes, since static fields are stored at Stan> their own addresses, separately from the instance.
A static field may itself be of a type with static fields. That doesn't
seem to be handled in this code... should it be? And if so, be careful
about the case where a class refers to itself recursively via static
fields; we still have some printing bugs in this area :(
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |