Mail Archives: djgpp-workers/2001/09/20/14:09:52
> gcc -D_USE_LIBM_MATH_H -D_HAVE_STDC -fno-builtin -O2 -g -nostdinc
> -Id:/djgpp.2/tests/cygnus -Id:/djgpp.2/tests/cygnus/../../include -c -o
> test.o test.c
>
> Exiting due to signal SIGSEGV
> General Protection Fault at eip=00000214
> eax=ffc9de35 ebx=9fff6cc0 ecx=00000004 edx=ffecc77d esi=0024483a
> edi=0022e963
> ebp=ffc9de1a esp=0000075c program=D:\DJGPP.2\BIN/gcc.exe
> cs: sel=02b7 base=02100000 limit=002cffff
> ds: sel=02bf base=02100000 limit=002cffff
> es: sel=02bf base=02100000 limit=002cffff
> fs: sel=028f base=00015fb0 limit=0000ffff
> gs: sel=0277 base=00000000 limit=0010ffff
> ss: sel=028f base=00015fb0 limit=0000ffff
> App stack: [000ae5b0..0002e5b0] Exceptn stack: [0002dff8..0002c0b8]
fs = ss and in DOS memory area. The only time our SS is there is very
early in startup (stub and transition to 32-bit code), using unixy
sbrk (but it's cs is also low base unless during transition), and during
final exit (also cs is low except during transition). Since EIP is
small, this is either a jump to bogus location or early in use of a
UPX image (are these UPXed?)
This may also indicate the exception handler is not set up yet in a
child and gcc caught the exception. Looking at register contents
we could probably find exactly where it's crashing. (Our debuggers
suppress reading the first 4K page, which must be re-enabled to debug
what's happening with UPX images).
> Operating system MS Windows NT 4.0 Wks + SP 6 (both with LFN driver or
> without give the same result)
Great, if reproducible we can find and fix.
> The files in the \djgpp\tests\cygnus directory compile with gcc-2.953 with
> no errors
Does this error happen with gcc (w/o make) on the above file?
> How could I help track down the problem ?
This is good help, I can see if I can reproduce this evening.
- Raw text -