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,  Xun Xun <xunxun1982@gmail.com>
Subject: Re: gdb with python support  still get crash on showing uninitialized local variables
Date: Thu, 16 Dec 2010 08:48:00 -0000	[thread overview]
Message-ID: <4D09D207.6080500@gmail.com> (raw)
In-Reply-To: <m3sjy0tn5b.fsf@fleche.redhat.com>

On 2010-12-14 23:00, Tom Tromey wrote:
> 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
Hi, Tom, Here are the good news.

  With the great help of Codeblocks' forum user "xunxun1982"
(http://forums.codeblocks.org/index.php?action=profile;u=12871), and 
several days testing and struggling. Now, the problem was totally solved.

In-fact, the problem is that the MSYS configure program can NOT 
correctly handling the Windows CR LF newline. When I use the MSYS Git to 
check out the git gdb working copy, all the source in the gdb working 
copy was encoded by CRLF format. and this cause many weird building 
errors. (since the snapshot of gdb source use LF format, so I can 
successfully build them).

Here are the steps to solve the problem:

1, open the file:
E:\PortableGit-1.7.3.1-preview20101002(1)\etc\gitconfig
and change the line
autocrlf = true
to
autocrlf = false

this can stop the git to change the style from LF to CRLF.

2, get the gdb git copy again (now, all the source was in UNIX LF style)

3, configure and make to build the gdb.


Now, everything works fine!!! I have successfully build the gdb from the 
git source under MSYS and MinGW 4.5.2. Wonderful!!!

asmwarrior










  reply	other threads:[~2010-12-16  8:48 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
     [not found]                   ` <4D06D1DB.1070501@gmail.com>
2010-12-14 15:00                     ` Tom Tromey
2010-12-16  8:48                       ` asmwarrior [this message]
     [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=4D09D207.6080500@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.com \
    --cc=xunxun1982@gmail.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