public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "xgsa at yandex dot ru" <sourceware-bugzilla@sourceware.org>
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: Wed, 09 Nov 2011 11:36:00 -0000	[thread overview]
Message-ID: <bug-13393-4717-Pey1B8pkwm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13393-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Anton <xgsa at yandex dot ru> 2011-11-09 11:36:30 UTC ---
Ok, I figured out that Qt Creator uses its own dumping system that relies on
python interface to gdb. So it just use "dynamic_type" property of gdb value
object. However, Eclipse CDT (and many other tools, I believe) uses standard MI
interface.

So I am wondering what is the preferable way to provide this information:
  - the "-var-create" command extension;
  - some another command creation;
  - "set print object" should affect MI interface;
  - some MI analogs of "set print object" command should be implemented;

-- 
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.


  parent reply	other threads:[~2011-11-09 11:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  8:31 [Bug mi/13393] New: " xgsa at yandex dot ru
2011-11-08 11:46 ` [Bug mi/13393] " xgsa at yandex dot ru
2011-11-08 16:42 ` tromey at redhat dot com
2011-11-08 16:56 ` andre.poenitz at nokia dot com
2011-11-08 21:38 ` xgsa at yandex dot ru
2011-11-09  7:17 ` andre.poenitz at nokia dot com
2011-11-09 11:36 ` xgsa at yandex dot ru [this message]
2011-11-09 13:19 ` andre.poenitz at nokia dot com
2011-11-09 15:26 ` tromey at redhat dot com
2011-11-10  9:10 ` xgsa at yandex dot ru
2011-11-10  9:12 ` xgsa at yandex dot ru
2011-11-10 21:06 ` tromey at redhat dot com
2011-11-11 20:14 ` xgsa at yandex dot ru
2011-11-28 17:14 ` xgsa at yandex dot ru
2011-11-28 17:17 ` xgsa at yandex dot ru
2011-11-28 17:33 ` andre.poenitz at nokia dot com
2011-11-28 17:56 ` xgsa at yandex dot ru
2011-12-02  9:30 ` xgsa at yandex dot ru
2011-12-02 17:17 ` xgsa at yandex dot ru
2011-12-02 19:01 ` tromey at redhat dot com
2011-12-02 19:04 ` tromey at redhat dot com
2011-12-16  8:08 ` xgsa at yandex dot ru
2011-12-16 14:49 ` tromey at redhat dot com
2012-04-14 12:19 ` cvs-commit at gcc dot gnu.org
2012-04-14 12:24 ` xgsa at yandex dot ru

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-13393-4717-Pey1B8pkwm@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).