Re: set print object on should affect MI varobjs (PR mi/13393)

[xgsa <xgsa@yandex.ru>]

Ping, guys! A few people reviewed this patch and said that it is ok in 
general, but there are a few minor comments. I have fixed them. Could 
somebody finally accept it?


Thanks,
Anton

-------- Original message --------
> I have run all the gdb test suites on my patch. There are no changes 
> (except of my new group adding). Testing was done on Linux32. So is it 
> ready for check in?
>
>
> Thanks,
> Anton
>
> -------- Original message --------
>> Hi,
>>> Hi.  ChangeLog nit:
>>> ...
>> Thanks, the similar case with update_dynamic_varobj_children is fixed 
>> too.
>>
>> The same patch and updated changelog are attached.
>>
>>
>> P.S. It seems the question with regression testing is left 
>> unanswered. Could someone clarify how it should be done or point me 
>> where I could read about it?
>>
>>
>> The original patch description:
>>
>> That patch makes "set print object" option affect MI interface. Here 
>> is an example:
>>
>> struct Base {
>>     Base() : a(1) {}
>>     virtual ~Base() {}  // Enforce type to have RTTI
>>     int a;
>> };
>>
>> struct Derived : public Base {
>>     Derived() : b(2) {}
>>     int b;
>> };
>>
>> int main() {
>>     Derived b;
>>     Base* aPtr = &b;
>>     return 0;                  // [1]
>> }
>>
>> Start gdb in MI mode and run to line [1]. Make -var-create for aPtr. 
>> If "set print object" is "on" you will see the type Derived* for the 
>> created varobj.
>>
>> See also more details here: 
>> http://sourceware.org/bugzilla/show_bug.cgi?id=13393
>>
>>
>> Thanks,
>> Anton.
>
>
>
>