Mail Archives: djgpp/1998/02/12/06:39:07
On Thu, 12 Feb 1998, Peter Palotas wrote:
> Enough space IS available on the directory pointed to by TEMP (both in
> environment and in DJGPP.ENV).
TEMP or TMPDIR? Bash uses the latter. Exactly how much free space is on
that disk? Is it RAM drive or a real disk?
> Okay, now from the GNU Hello 1.3 package (as downloaded from a the simtel
> mirror at ftp.sunet.se today) when trying to run configure from within bash
> in a DOS box from withing windows I get the following:
>
> bash$ ./configure
That's not how you are supposed to configure hello for DJGPP! There is
config.bat in the djgpp/ directory, and a patched configure script in the
same directory that the batch file runs. Please read the file README.dos
in the distribution and do what it tells.
> Exiting due to signal SIGSEGV
> Page fault at eip=0000a1ba, error=0004
> eax=00181900 ebx=00181900 ecx=ffffffff edx=00000000 esi=00000000 edi=00000000
> ebp=0016b6e8 esp=0016b6d4 program=D:\CODING\DJGPP\BIN/bash.exe
This means a null pointer dereference. Please insert "set -x" at the
beginning of the script and see what line does it execute when it
crashes.
> > - does Bash crash every time you run that script, or only
> > sometimes?
> I guess the answer to this must be NO, since it doesn't CRASH under windows
> 3.11.
But does it always crash on DOS with that script? (The fact that it
doesn't crash on Windows is irrelevant: Windows doesn't catch null
pointer dereferences like CWSDPMI does. However, the message printed by
Bash under Windows clearly tells that some function gets a null pointer,
so the same problem exists on both Windows and DOS.)
> Yes, maybe the script won't work anyway, but I still don't think bash
> should crash!
It doesn't unless you give it a reason that is good enough ;-).
- Raw text -