This is the mail archive of the
gdb@sourceware.org
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: asmwarrior <asmwarrior at gmail dot com>
- Cc: Eli Zaretskii <eliz at gnu dot org>, gdb at sourceware dot org
- Date: Mon, 15 Nov 2010 11:10:20 -0700
- Subject: Re: gdb with python support still get crash on showing uninitialized local variables
- References: <4CB66700.3000907@gmail.com> <m3tykn2id8.fsf@fleche.redhat.com> <m3fww2ued0.fsf_-_@fleche.redhat.com> <4CBE7B08.9060905@gmail.com> <m3eibidolr.fsf@fleche.redhat.com> <83bp6l9b4l.fsf@gnu.org> <4CD8ABA4.2090304@gmail.com> <m3eiaq5s59.fsf@fleche.redhat.com> <4CE0C149.6090609@gmail.com>
>>>>> ">" == ext asmwarrior <asmwarrior@gmail.com> writes:
>> the attachment is the config.log file under libiberty
>> I know little about automake system.
>> Hope it will help to find the bug.
Apparently HAVE_STDLIB_H is defined after all.
So, I'm afraid I don't know what is going on.
Tom