Mail Archives: djgpp/2002/04/07/06:32:27
On Sat, 6 Apr 2002, Tina wrote:
> When I run a dj-complied exe program. I always get the
> following information:
>
> Exiting due to signal SIGSEGV
> Page fault at eip=65726574, error=0004
> eax=00000001 ebx=000086ef ecx=00000000 edx=0000033f esi=00000054 edi=0003d3fc
> ebp=00459fa8 esp=00459f9c program=C:\DJ\MAIN.EXE
> cs: sel=00a7 base=86ef4000 limit=ffd7afff
> ds: sel=00af base=86ef4000 limit=ffd7afff
> es: sel=00af base=86ef4000 limit=ffd7afff
> fs: sel=0087 base=00008240 limit=0000ffff
> gs: sel=00c7 base=00000000 limit=0010ffff
> ss: sel=00af base=86ef4000 limit=ffd7afff
> App stack: [0045a000..003da000] Exceptn stack:
> [0003d35c..0003b41c]
>
> Call frame traceback EIPs:
> 0x65726574
> 0x00027554
> 0x0002b082
In a nutshell: your program has a bug. It crashes because it tried to
access an address that is not part of the program's address space. In
other words, some pointer is garbled.
In this case, the EIP register, the instruction pointer, has the garbled
value 0x65726574. This value seems to be part of some ASCII text
("tere", little-endian). Does that text ring a bell?
The DJGPP FAQ list descdribes in section 12.2 how to start debugging your
program using the information in the crash message.
- Raw text -