From: Tom Tromey <tromey@redhat.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: "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: Fri, 22 Oct 2010 19:13:00 -0000 [thread overview]
Message-ID: <m3eibidolr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4CBE7B08.9060905@gmail.com> (asmwarrior@gmail.com's message of "Wed, 20 Oct 2010 13:15:52 +0800")
>>>>> "asmwarrior" == asmwarrior <asmwarrior@gmail.com> writes:
asmwarrior> I just use git to check out the latest whole gdb source (>100M)
asmwarrior> Then apply your patch
asmwarrior> Then use MSYS + MINGW GCC 4.4.4 to build it .
asmwarrior> But I failed with the build error. like:
That seems weird, like maybe you are missing a header file.
I don't know for certain what it is, though; you'll have to debug it.
asmwarrior> /bin/sh: line 1: ../../../../src/gdb/bfd/../mkinstalldirs: Permission denied
This file should be +x.
Tom
next prev parent reply other threads:[~2010-10-22 19:13 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 ` gdb with python support still get crash on showing uninitialized local variables asmwarrior
2010-10-22 19:13 ` Tom Tromey [this message]
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=m3eibidolr.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).