Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: asmwarrior <asmwarrior@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
Subject: Re: gdb with python support  still get crash on showing uninitialized local variables
Date: Tue, 14 Dec 2010 02:13:00 -0000	[thread overview]
Message-ID: <4D06D28B.7050409@gmail.com> (raw)
In-Reply-To: <m3wroemp9v.fsf@fleche.redhat.com>

On 2010-11-16 2:10, Tom Tromey wrote:
>> Apparently HAVE_STDLIB_H is defined after all.
>> So, I'm afraid I don't know what is going on.
>>
>> Tom


Hi, Tom, After struggling with the building gdb, I finally found a very 
strange build problem.

under MSYS and MinGW 4.4.5.

Today, I can build the gdb source from the snapshot: 
gdb-7.2.50.20101213.tar.bz2
I have already released in the codeblocks' forum post:

http://forums.codeblocks.org/index.php/topic,11301.0.html


But the real strange thing is: I failed build the gdb from the git 
working copy.
The error is just like the same as I reported several days ago. that is:
--------------------------------------------------------------------------------
of built-in function 'free'
../../gdb/libiberty/fibheap.c: In function 'fibheap_extract_min':
../../gdb/libiberty/fibheap.c:
190:7: warning: incompatible implicit declaration

of built-in function 'free'
../../gdb/libiberty/fibheap.c: In function 'fibheap_replace_key_data':
../../gdb/libiberty/fibheap.c:220:30: error: 'LONG_MIN' undeclared 
(first use in
  this function)
../../gdb/libiberty/fibheap.c:220:30: note: each undeclared identifier 
is report
ed only once for each function it appears in
../../gdb/libiberty/fibheap.c: In function 'fibheap_delete_node':
../../gdb/libiberty/fibheap.c:261:36: error: 'LONG_MIN' undeclared 
(first use in
  this function)
../../gdb/libiberty/fibheap.c:265:7: warning: implicit declaration of 
function '
abort'
../../gdb/libiberty/fibheap.c:265:7: warning: incompatible implicit 
declaration

of built-in function 'abort'
../../gdb/libiberty/fibheap.c: In function 'fibheap_delete':
../../gdb/libiberty/fibheap.c:277:5: warning: incompatible implicit 
declaration

of built-in function 'free'
../../gdb/libiberty/fibheap.c: In function 'fibheap_consolidate':
../../gdb/libiberty/fibheap.c:368:3: warning: implicit declaration of 
function '
memset'
../../gdb/libiberty/fibheap.c:368:3: warning: incompatible implicit 
declaration
of built-in function 'memset'
make[2]: *** [fibheap.o] Error 1

make[2]: Leaving directory `/e/test/build/libiberty'
make[1]: *** [all-libiberty] Error 2
make[1]: Leaving directory `/e/test/build'
make: *** [all] Error 2
--------------------------------------------------------------------------------

I have both a folder named "gdb" (this is the git working copy)
and a folder named "gdb-7.2.50.20101213" (this is unzipped snapshot)

Then this command works:

cd build
../gdb-7.2.50.20101213/configure --prefix=/E/test/install 
--build=mingw32 --host=mingw32 --target=mingw32 \
    CFLAGS="-s -L/python/libs -I/python/include 
-I/E/test/expat/install/include -static -L/E/test/expat/install/lib" \
    --with-python \
    --with-expat
make
---------------------------------------------------------------------------------

But this command failed with the error I shown above:

cd build
../gdb/configure --prefix=/E/test/install --build=mingw32 --host=mingw32 
--target=mingw32 \
    CFLAGS="-s -L/python/libs -I/python/include 
-I/E/test/expat/install/include -static -L/E/test/expat/install/lib" \
    --with-python \
    --with-expat
make

----------------------------------------------------------------------------------

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?

thanks.

asmwarrior




  reply	other threads:[~2010-12-14  2:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14  2:16 asmwarrior
2010-10-14 18:30 ` André Pönitz
2010-10-15  3:55   ` asmwarrior
2010-10-15 22:38   ` Tom Tromey
2010-11-05 17:14     ` André Pönitz
2010-10-15 22:37 ` Tom Tromey
2010-10-16  1:14   ` asmwarrior
     [not found]   ` <m3fww2ued0.fsf_-_@fleche.redhat.com>
2010-10-20  5:19     ` asmwarrior
2010-10-20  5:33       ` asmwarrior
2010-10-22 19:13       ` Tom Tromey
2010-10-22 21:22         ` Eli Zaretskii
2010-10-29 19:18           ` Joel Brobecker
2010-10-29 22:01             ` Eli Zaretskii
2010-10-31  2:24               ` asmwarrior
2010-11-09  2:06           ` asmwarrior
2010-11-12 18:07             ` Tom Tromey
     [not found]               ` <4CE0C149.6090609@gmail.com>
2010-11-15 18:10                 ` Tom Tromey
2010-12-14  2:13                   ` asmwarrior [this message]
     [not found]                   ` <4D06D1DB.1070501@gmail.com>
2010-12-14 15:00                     ` Tom Tromey
2010-12-16  8:48                       ` asmwarrior
     [not found]     ` <AANLkTinsJLTZT0ws=LbpYcq85_Z9_R=fcXz+J+kqScJU@mail.gmail.com>
2010-12-17 19:04       ` RFA: add python exception subclasses Tom Tromey
2010-12-18  2:26         ` asmwarrior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D06D28B.7050409@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox