gdb with python support still get crash on showing uninitialized local variables

[asmwarrior]

  thanks for the reply.

On 2010-10-15 2:29, André Pönitz wrote:
> 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:
I'm Sorry for the inconvience.

> 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.'
Aha, Seems gdb works better in Linux system than Windows.

> 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.
fully agree, Hopefully the GDB gurus can fix it.

Asmwarrior