From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15016 invoked by alias); 29 Oct 2010 22:01:41 -0000 Received: (qmail 14995 invoked by uid 22791); 29 Oct 2010 22:01:40 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout23.012.net.il (HELO mtaout23.012.net.il) (80.179.55.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 29 Oct 2010 22:01:34 +0000 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0LB200300NCPM000@a-mtaout23.012.net.il>; Sat, 30 Oct 2010 00:01:31 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.126.229.202]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LB2003W6NUHG470@a-mtaout23.012.net.il>; Sat, 30 Oct 2010 00:01:31 +0200 (IST) Date: Fri, 29 Oct 2010 22:01:00 -0000 From: Eli Zaretskii Subject: Re: gdb with python support still get crash on showing uninitialized local variables In-reply-to: <20101029191820.GA2936@adacore.com> To: Joel Brobecker Cc: tromey@redhat.com, asmwarrior@gmail.com, gdb@sourceware.org, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <8362wk7j5r.fsf@gnu.org> References: <4CB66700.3000907@gmail.com> <4CBE7B08.9060905@gmail.com> <83bp6l9b4l.fsf@gnu.org> <20101029191820.GA2936@adacore.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-10/txt/msg00395.txt.bz2 > Date: Fri, 29 Oct 2010 15:18:20 -0400 > From: Joel Brobecker > Cc: Tom Tromey , asmwarrior@gmail.com, gdb@sourceware.org, gdb-patches@sourceware.org > > Yes, because it's a script, the makefile should execute it via $SHELL. > I see that we're making the same error in gdb/doc, for instance, so > it looks like we would be unable to build the documentation if building > using MinGW tools. If you are using the MinGW port of GNU Make, it will always use sh.exe (if it can find it on your PATH) automatically to run any shell scripts invoked by the Makefile. I just tried that with a MinGW build of Make 3.82, and commands like "./mkinstalldirs foo/bar" just work (I do have a sh.exe). This works because the function process_begin on w32/subproc/sub_proc.c has code to detect a Unix shell script and DTRT. So there's some other factor at work here. Or maybe the sh.exe which is installed on the OP's machine has some issues that mine doesn't.