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: Tue, 14 Dec 2010 08:00:32 -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> <m3wroemp9v.fsf@fleche.redhat.com> <4D06D1DB.1070501@gmail.com>
>>>>> ">" == ext asmwarrior <asmwarrior@gmail.com> writes:
>> Today, I can build the gdb source from the snapshot:
>> gdb-7.2.50.20101213.tar.bz2
>> But the real strange thing is: I failed build the gdb from the git
>> working copy.
>> by the way, the gdb git address I'm using is:
>> git clone git://sourceware.org/git/gdb.git
>> list here:
>> http://www.gnu.org/software/gdb/current/
>> Any ideas?
I don't know of any problem offhand. I do builds from the git mirror
regularly without problems, but of course I'm on a different host.
All I can suggest is to debug it.
If I had this problem I might start by comparing the snapshot and git
source trees. Though, TBH, I'd be surprised to find anything weird
there.
Next I would try to understand why exactly the build failed in
libiberty, and track down the problem.
Tom