This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gdb with python support still get crash on showing uninitialized local variables


> Date: Fri, 29 Oct 2010 15:18:20 -0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Tom Tromey <tromey@redhat.com>, 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]