This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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.3000907@gmail.com> <201010142029.24092.andre.poenitz@nokia.com>

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

References:
- gdb with python support still get crash on showing uninitialized local variables
  - From: asmwarrior
- Re: gdb with python support still get crash on showing uninitialized local variables
  - From: AndrÃ PÃnitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]