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

["pmuldoon at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

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

Phil Muldoon <pmuldoon at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andre.poenitz at nokia dot
                   |                            |com, dodji at redhat dot
                   |                            |com, marc.khouzam at
                   |                            |ericsson dot com, pmuldoon
                   |                            |at redhat dot com, tromey
                   |                            |at redhat dot com, vladimir
                   |                            |at codesourcery dot com
   Target Milestone|---                         |7.4

--- Comment #3 from Phil Muldoon <pmuldoon at redhat dot com> 2011-04-18 09:56:56 UTC ---
I gratuitously added a few people to this bug.  Apologies if you don't
care/don't want to be CC'd.  I wanted a sample MI audience, vlad and tom to
comment.  It seems to me that we will be forever plagued Python by pretty
printers trying to interpret uninitialized data.  I think Jens idea is good. 
We could add a --limit=100 optional flag to some MI commands and list this as a
feature via the MI features mechanism.  What MI commands would need this? 
Would we limit it by byte, or by (wide) char?

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