ct: Re: Guidance needed: hi-level steps to track an object until its
> destruction
> To: "Jeff Saremi"
> Cc: gcc@gcc.gnu.org
> Received: Saturday, August 28, 2010, 1:05 PM
> On Thu, 2010-08-26 at 18:16 -0700,
> Jeff Saremi wrote:
> > I'm hoping someone here could
I'm hoping someone here could take the time to outline what I need to do (i'm
not looking for code but if you point me to some i'd appreciate it).
I'd like to track an object from the it's created until it's destroyed (in
C++). And then see if a certain method of it is called or not. To keep it
well, that explains it nicely. thanks
I wanted to go through declarations in a function and print them out so as to
get more familiar with them before being able to manipulate them.
I wrote this function as a plugin; it successfully writes out all statements
but mysteriouslty the declarations are missing. What am I missing? Is there
Daniel/Andrew
thanks so much. I was using gdb version 7.1. So it understood deferred
breakpoints but as long as I started gdb with something like ~/bin/gcc it never
stopped in my function.
As soon as I switched to running gdb on cc1, it worked!
Now i can work on debugging the seg-fault i'm causin
Sending this to "gcc" since I got no help from sending it to "gcc-help"
--- On Sun, 8/8/10, Jeff Saremi wrote:
> From: Jeff Saremi
> Subject: Debugging plugins with gdb
> To: gcc-h...@gcc.gnu.org
> Date: Sunday, August 8, 2010, 9:52 AM
> I'd like to ste
