public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jens.elmenthaler at verigy dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/12555] Hangup in MI commands if python StdStringPrinter used on uninitialized std::string
Date: Wed, 09 Mar 2011 16:09:00 -0000	[thread overview]
Message-ID: <bug-12555-4717-ne2qdBVBJd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <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.


  reply	other threads:[~2011-03-09 16:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 16:03 [Bug mi/12555] New: " jens.elmenthaler at verigy dot com
2011-03-09 16:09 ` jens.elmenthaler at verigy dot com [this message]
2011-03-09 16:16 ` [Bug mi/12555] " jens.elmenthaler at verigy dot com
2011-04-18  9:58 ` pmuldoon at redhat dot com
2011-04-18 10:31 ` andre.poenitz at nokia dot com
2011-04-18 10:59 ` pmuldoon at redhat dot com
2011-04-18 11:41 ` andre.poenitz at nokia dot com
2011-04-18 14:25 ` dodji at seketeli dot org
2011-04-18 16:15 ` marc.khouzam at ericsson dot com
2011-11-10 21:35 ` tromey at redhat dot com
2011-12-07 13:04 ` xgsa at yandex dot ru
2013-07-04 19:51 ` aegges at web dot de
2023-08-31 17:20 ` tromey at sourceware dot org

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-12555-4717-ne2qdBVBJd@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).