Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: asmwarrior <asmwarrior@gmail.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>,  gdb-patches@sourceware.org
Subject: Re: gdb with python support  still get crash on showing uninitialized local variables
Date: Wed, 20 Oct 2010 05:19:00 -0000	[thread overview]
Message-ID: <4CBE7B08.9060905@gmail.com> (raw)
In-Reply-To: <m3fww2ued0.fsf_-_@fleche.redhat.com>

On 2010-10-20 4:17, Tom Tromey wrote:
 > reading variable s (Cannot access memory at address 0x80)
 > Tom> I am working on a fix for this.
 >
 > Tom> Currently all gdb exceptions are convert to a Python 
RuntimeError.  But,
 > Tom> I think we should differentiate a little more.  In particular, I 
think a
 > Tom> gdb MEMORY_ERROR should be a separate class, and should be handled
 > Tom> specially by the pretty-printing code (basically by omitting the 
stack
 > Tom> trace).
 >
 > This patch implements this idea.  It adds some new subclasses of
 > RuntimeError, including one specifically for MEMORY_ERROR.  Then it
 > arranges for the memory error exception to be treated specially by the
 > pretty-printing code.
 >
 > Built and regtested on x86-64 (compile farm).
 > Some new test cases are included.
 >
 > asmwarrior, it would be helpful if you could try this out.
 >
 > Ok?
 >
 > Tom
 >
OK.


I just use git to check out the latest whole gdb source (>100M)
Then apply your patch

Then use MSYS + MINGW GCC 4.4.4 to build it .

But I failed with the build error. like:

../../gdb/libiberty/fibheap.c:151: warning: incompatible implicit 
declaration of
  built-in function 'free'
../../gdb/libiberty/fibheap.c:156: warning: incompatible implicit 
declaration of
  built-in function 'free'
../../gdb/libiberty/fibheap.c:172: warning: incompatible implicit 
declaration of
  built-in function 'free'
../../gdb/libiberty/fibheap.c: In function 'fibheap_extract_min':
../../gdb/libiberty/fibheap.c:190: warning: incompatible implicit 
declaration of
  built-in function 'free'
../../gdb/libiberty/fibheap.c: In function 'fibheap_replace_key_data':
../../gdb/libiberty/fibheap.c:220: error: 'LONG_MIN' undeclared (first 
use in th
is function)
../../gdb/libiberty/fibheap.c:220: error: (Each undeclared identifier is 
reporte
d only once
../../gdb/libiberty/fibheap.c:220: error: for each function it appears in.)
../../gdb/libiberty/fibheap.c: In function 'fibheap_delete_node':
../../gdb/libiberty/fibheap.c:261: error: 'LONG_MIN' undeclared (first 
use in th
is function)
../../gdb/libiberty/fibheap.c:265: warning: implicit declaration of 
function 'ab
ort'
../../gdb/libiberty/fibheap.c:265: warning: incompatible implicit 
declaration of
  built-in function 'abort'
../../gdb/libiberty/fibheap.c: In function 'fibheap_delete':
../../gdb/libiberty/fibheap.c:277: warning: incompatible implicit 
declaration of
  built-in function 'free'
../../gdb/libiberty/fibheap.c: In function 'fibheap_consolidate':
../../gdb/libiberty/fibheap.c:368: warning: implicit declaration of 
function 'me
mset'
../../gdb/libiberty/fibheap.c:368: 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

When I manually add this macro definition then continue the build, I got 
other more errors.

I can remember that the snapshot of GDB source 20101005, I can build it 
successful. I'm not sure why.

Asmwarrior.

BTW:

My friend Loaden has some build errors when building gdb.exe (weekly 
20101019) from linux, here is his build log:

  /bin/install -c -m 644 ../../../../src/gdb/bfd/doc/bfd.info 
'/home/loaden/gdb/share/info'
  install-info --info-dir='/home/loaden/gdb/share/info' 
'/home/loaden/gdb/share/info/bfd.info'
make[4]: Leaving directory `/home/loaden/AUR/gdb/build/gdb-win/bfd/doc'
Making install in po
make[4]: Entering directory `/home/loaden/AUR/gdb/build/gdb-win/bfd/po'
if test -r ../../../../src/gdb/bfd/../mkinstalldirs; then \
       ../../../../src/gdb/bfd/../mkinstalldirs /home/loaden/gdb/share; \
     else \
       ../../../../src/gdb/bfd/mkinstalldirs /home/loaden/gdb/share; \
     fi
/bin/sh: line 1: ../../../../src/gdb/bfd/../mkinstalldirs: Permission denied
make[4]: *** [install-data-yes] Error 126
make[4]: Leaving directory `/home/loaden/AUR/gdb/build/gdb-win/bfd/po'
make[4]: Entering directory `/home/loaden/AUR/gdb/build/gdb-win/bfd'
make[5]: Entering directory `/home/loaden/AUR/gdb/build/gdb-win/bfd'
make[5]: Nothing to be done for `install-exec-am'.
test -z "/home/loaden/gdb/include" || /bin/mkdir -p 
"/home/loaden/gdb/include"
  /bin/install -c -m 644 bfd.h 
../../../src/gdb/bfd/../include/ansidecl.h 
../../../src/gdb/bfd/../include/symcat.h 
../../../src/gdb/bfd/../include/bfdlink.h '/home/loaden/gdb/include'
test -z "/home/loaden/gdb/lib" || /bin/mkdir -p "/home/loaden/gdb/lib"
  /bin/sh ./libtool   --mode=install /bin/install -c   libbfd.la 
'/home/loaden/gdb/lib'
libtool: install: /bin/install -c .libs/libbfd.lai 
/home/loaden/gdb/lib/libbfd.la
libtool: install: /bin/install -c .libs/libbfd.a 
/home/loaden/gdb/lib/libbfd.a
libtool: install: chmod 644 /home/loaden/gdb/lib/libbfd.a
libtool: install: i686-mingw32-ranlib /home/loaden/gdb/lib/libbfd.a
libtool: install: warning: remember to run `libtool --finish 
/home/loaden/AUR/gdb/depends/lib'
make[5]: Leaving directory `/home/loaden/AUR/gdb/build/gdb-win/bfd'
make[4]: Leaving directory `/home/loaden/AUR/gdb/build/gdb-win/bfd'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory `/home/loaden/AUR/gdb/build/gdb-win/bfd'
make[2]: *** [install] Error 2
make[2]: Leaving directory `/home/loaden/AUR/gdb/build/gdb-win/bfd'
make[1]: *** [install-bfd] Error 2
make[1]: Leaving directory `/home/loaden/AUR/gdb/build/gdb-win'
make: *** [install] Error 2





  parent reply	other threads:[~2010-10-20  5:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4CB66700.3000907@gmail.com>
     [not found] ` <m3tykn2id8.fsf@fleche.redhat.com>
2010-10-19 20:17   ` RFA: add python exception subclasses (Was: gdb with python support still get crash on showing uninitialized local variables) Tom Tromey
2010-10-19 21:13     ` Eli Zaretskii
2010-10-20  5:19     ` asmwarrior [this message]
2010-10-22 19:13       ` gdb with python support still get crash on showing uninitialized local variables 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-12 20:47     ` RFA: add python exception subclasses Tom Tromey
     [not found]     ` <AANLkTinsJLTZT0ws=LbpYcq85_Z9_R=fcXz+J+kqScJU@mail.gmail.com>
2010-12-17 19:04       ` 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=4CBE7B08.9060905@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    /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