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: "jens.elmenthaler at verigy dot com"<sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 9 Mar 2011 16:09:42 +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 #1 from Jens Elmenthaler <jens.elmenthaler at verigy dot com> 2011-03-09 16:09:28 UTC ---
A couple of observations:
1) I altered StdStringPrinter to not retrieve more than 100 chars in its
to_string methods, and I don't see any hangups any longer.
2) There is no hangup if I use gdb's command line instead of a graphical
frontend. This is because the command line interface has a user setting for the
number of characters to fetch for strings.
3) The hangup is not just limited to -stack-list-locals, it can be any MI
command that tries to return the value of a local, an expression, or MI
variable
--
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.