public inbox for
help / color / mirror / Atom feed
From: "marc.khouzam at ericsson dot com" <>
Subject: [Bug mi/12555] Hangup in MI commands if python StdStringPrinter used on uninitialized std::string
Date: Mon, 18 Apr 2011 16:15:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #7 from Marc Khouzam <marc.khouzam at ericsson dot com> 2011-04-18 16:13:57 UTC ---
(In reply to comment #6)
> I still think having a default limit that leave gdb itself (and a frontend
> using it) in a usable state would make sense. 
> Limiting the size of dumped data to something that finishes dumping in
> acceptable time (less than a few seconds in total, given the uncertain number
> of items to display a single display should be well under a second) seems to be
> a good first approximation at least as long as the data dumping is not
> interruptible (see 12615).
> Anyway, if you think the frontend should be required to use --limit=100, so be
> it.
> To the second issue: I don't think the assumption that data display can be
> sensibly steered by keeping track of entering and leaving stack frames or block
> scopes holds true. Both debugging itself and background activities might (and
> typically do) result in changed displays.

I agree with Andre.  Eclipse blindly asks GDB for values of variables and has
no idea of a variable has been initialized or not.  Therefore, if adding
--limit is the proper way to fix this issue, Eclipse will always use --limit;
so, if a FE always uses a flag, it makes me think having a default would make

BTW, thanks for dealing with this issue, PrettyPrinting is one of the very nice
new features we are happy to make use of.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2011-04-18 16:15 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
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 [this message]
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:

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

  git send-email \ \ \ \

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