This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug mi/12555] Hangup in MI commands if python StdStringPrinter usedon uninitialized std::string
- From: "pmuldoon at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 18 Apr 2011 10:58:24 +0000
- Subject: [Bug mi/12555] Hangup in MI commands if python StdStringPrinter usedon uninitialized std::string
- Auto-submitted: auto-generated
- References: <bug-12555-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12555
--- Comment #5 from Phil Muldoon <pmuldoon at redhat dot com> 2011-04-18 10:53:39 UTC ---
I don't think we should limit it by default. As this would be an optional
switch, the default would be unlimited. But a way for FEs to actually instruct
GDB/MI not to fetch any more than a sample is a good idea. Per command. I'm
guessing this would really only be used when a new frame/block is entered and
the FE wants a representation of the variables in there without actually
fetching (much of) the uninitialized data?
I hack on the Python side of GDB, and I don't know a tremendous amount of MI,
and even less what MI consumers really want. But this feature with Python GDB
pretty-printers is a persistent pain. What do you all want?
--
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.