This is the mail archive of the
mailing list for the GDB project.
Re: gdb with python support still get crash on showing uninitialized local variables
- From: asmwarrior <asmwarrior at gmail dot com>
- To: AndrÃ PÃnitz <andre dot poenitz at nokia dot com>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Fri, 15 Oct 2010 11:51:12 +0800
- Subject: Re: gdb with python support still get crash on showing uninitialized local variables
- References: <4CB66700.email@example.com> <firstname.lastname@example.org>
thanks for the reply.
On 2010-10-15 2:29, AndrÃ PÃnitz wrote:
I'm Sorry for the inconvience.
I'll take that direct CC: to me as a hint that I should comment. Not sure
this is a good idea, but here we go:
Aha, Seems gdb works better in Linux system than Windows.
Works fine for me using Qt Creator on Linux, gdb 7.1, 7.2 and recent CVS,
including (our non-gdb) Python based pretty printing.'
fully agree, Hopefully the GDB gurus can fix it.
This looks like gdb's own pretty printers could make more use of
try/except and perhaps a few sanity checks on the contents.
Printing "std::vector of length -37952" does not make much sense.