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: Tom Tromey <tromey at redhat dot com>
- To: AndrÃ PÃnitz <andre dot poenitz at nokia dot com>
- Cc: ext asmwarrior <asmwarrior at gmail dot com>, "pmuldoon\ at redhat dot com" <pmuldoon at redhat dot com>, "gdb\ at sourceware dot org" <gdb at sourceware dot org>
- Date: Fri, 15 Oct 2010 16:38:23 -0600
- Subject: Re: gdb with python support still get crash on showing uninitialized local variables
- References: <4CB66700.email@example.com> <firstname.lastname@example.org>
>>>>> "AndrÃ" == AndrÃ PÃnitz <email@example.com> writes:
AndrÃ> However, I do not use the gdb version of the pretty printers for
AndrÃ> the stability reason you just encountered, and because they
AndrÃ> cannot (easily...) create several layers including possibly
AndrÃ> "virtual" ones that do not correspond to actual objects on the
AndrÃ> inferior side.
I don't understand this latter comment, but I would like to.
Could you give an example? Or explain it in more depth?