[Bug mi/13393] There is no way to access runtime type of C++ variable via MI (using RTTI)

["tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=13393

--- Comment #18 from Tom Tromey <tromey at redhat dot com> 2011-12-02 19:00:51 UTC ---
(In reply to comment #12)
> Created attachment 6076 [details]

> - indirect pointers (I mean pointer to pointer or reference to pointer and so
> on) do not have a real type in whatis/print commands. The proposed patch does
> not fix this problem because there is another problem in gdb which does not
> allow to cast pointer to reference to pointer ("T*" => "T*&"). If it will be
> fixed it is quite easy to provide support of indirect references too (a few
> changes in value_rtti_target_type() should be enough).

Please file a separate bug for the cast problem.

> - the last unresolved problem is type update when value changed. I am not sure
> about how it should be done. Should we just set "type_changed" & "new_type"
> properties in the result of -var-update command? If so I think not all
> frontends will support it (at least Eclipse will not - I have checked it). Or
> maybe we should create dynamic varobj some how? Can somebody advice me
> something about it?

I think it is fine to add new fields to varobj without expecting all front
ends to immediately respect them.  So, emitting type_changed and new_type is
fine.  Front ends are supposed to ignore fields they don't understand.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.