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: Fri, 12 Nov 2010 11:11:14 -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>
>>>>> ">" == asmwarrior <asmwarrior@gmail.com> writes:
>> Dear GDB gurus, Today, I just do a git pull, then try to build the gdb
>> again. but I still failed under building gdb under windows/msys.
>> ../../gdb/libiberty/fibheap.c: In function 'fibheap_union':
>> ../../gdb/libiberty/fibheap.c:151: warning: implicit declaration of
>> function 'free'
It sounds like HAVE_STDLIB_H is not defined.
libiberty's config.log might show why.
Tom