Mail Archives: djgpp-workers/2001/09/20/11:58:22
On Thu, 20 Sep 2001, Wojciech Galazka wrote:
> 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]
That's a weirdo one: EBP and ESP are screwed up, and SS is loaded with a
segment that isn't ours. To say nothing of EIP, which is in the null
page.
> I tried symify but there is no debug info in gcc.exe
symify would not help even if gcc was unstripped: the EIP is outside any
valid code and SS:SP aren't pointing to our stack, so you have no hope of
getting a traceback.
> How could I help track down the problem ?
I'd suggest to build the same version of GCC with stock v2.03, and see if
that binary crashes or not.
Is it possible that the way you installed this GCC version somehow mixes
up files from different GCC distributions? Or did you completely
replaced your compiler with this version?
- Raw text -