[antlr-interest] C/C++ instrumentation tool

[Peggy Fieland]

You're right about the watchpoints -- but for Andy's
purposes a simpler solution might suffice. 
Personally, I wouldn't trace all changes to variables
in any case -- I've found in general the amount of
data is too overwelming.

Peggy
--- Paul Johnson <gt54-antlr at cyconix.com> wrote:

> Peggy Fieland wrote:
> > You can attach a command macro to any breakpoint:
> > 
> > Break foo
> > commands (hit enter)
> > GDB will reply to enter the list of commands,
> ending
> > with a line with END (see below for my example)
> 
> I'm not a gdb expert, but I think you could waste a
> lot of time and get 
> nowhere here. In principle, you can create
> watchpoints for all your 
> variables. You could then add all your variables to
> the auto display 
> list ('display'). You could then define 'hook-stop'
> to automatically 
> restart (put a 'continue' in there) every time gdb
> stops. This would 
> automate collection and display, but you then have
> the problem that you 
> have to set new watchpoints for every new scope, and
> they're 
> automatically deleted when they go out of scope.
> 
> This should be handled with tracepoints, but I don't
> think you'll do any 
> better with them; they don't seem to be completely
> implemented yet.
> 
> Paul
> 
>