[Bug mi/12555] Hangup in MI commands if python StdStringPrinter used on uninitialized std::string

["marc.khouzam at ericsson dot com" <sourceware-bugzilla@sourceware.org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=12555

--- 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
sense.

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: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.