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:16:00 -0000	[thread overview]
Message-ID: <bug-12555-4717-Pix9FtVgSg@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 #2 from Jens Elmenthaler <jens.elmenthaler at verigy dot com> 2011-03-09 16:16:09 UTC ---
Some thoughts on how to circumvent such hangups:

I don't think that pretty printers for strings should implement a limit on the
max number of chars to fetch, this should be controlled by the frontend, as the
gdb command line has its own user setting for the limit

This would lead to a MI command that lets the frontend adjust such a limit.

-- 
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-03-09 16:16 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 ` [Bug mi/12555] " jens.elmenthaler at verigy dot com
2011-03-09 16:16 ` jens.elmenthaler at verigy dot com [this message]
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-Pix9FtVgSg@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).