This is the mail archive of the 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: MI: type prefixes for values

On Friday 07 April 2006 21:37, Jim Ingham wrote:
> Yes, it looks like we added that.  Our -stack-list-frames looks like:
> 553^done,stack=[frame=
> {level="0",addr="0x00003db0",fp="0xbffff2c0",func="main",file="/
> private/nfsroot/Users/jingham/Projects/ManyThreads/main.m",fullname="/
> private/nfsroot/Users/jingham/Projects/ManyThreads/
> main.m",line="64",dir="/private/nfsroot/Users/jingham/Projects/
> ManyThreads/"}]

Hi Jim,
I've now got one last questions. Why do you do this managements of variable 
objects in XCode, and not on gdb side, using -var-update?

If I understand correctly, each time program stops, we need to know for each 
variable object if:

   - it's still alive (containing frame has not exited)
   - changed the value
   - is in different frame from the current (when we enter the function)
   - if the expression variable object was created with refers to 
     different variables now (say, if you created varobj for global 'i',
     now just entered a block containing local 'i').

In mainline, -var-update handles the first two points already. It's possible 
to support third point easily. I'm not sure about the fourth.

So, why did you decide to handle varobj lifetime in XCode, and not in gdb? 


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