From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18049 invoked by alias); 2 Dec 2011 19:01:13 -0000 Received: (qmail 18024 invoked by uid 22791); 2 Dec 2011 19:01:12 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 02 Dec 2011 19:00:55 +0000 From: "tromey at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug mi/13393] There is no way to access runtime type of C++ variable via MI (using RTTI) Date: Fri, 02 Dec 2011 19:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: mi X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2011-q4/txt/msg00439.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=13393 --- Comment #18 from Tom Tromey 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.