Mail Archives: djgpp/1999/10/27/11:21:34
Forsberg Sakari writes:
> Call frame traceback EIPs:
> 0x0002ba7b _gettextinfo+567
> 0x0002baaf _gettextinfo+619
> 0x0002bb3b _gettextinfo+759
> 0x0002bc70 __set_screen_lines+300
> 0x00027d32 _term_init+82. line 259 of iodjgpp.c
> 0x0000e652 _main+1250, line 396 of fed.c
> 0x0002a36a ___crt1_startup+174
That's very strange, and starts to look like it might be a libc
problem, since there is nothing at all unusual about the way FED
calls these routines.
The strangest thing of all is that looking in conio.c, the
_set_screen_lines() function doesn't even call gettextinfo()!
It does call _gettextinfo(), but that's not what shows up in
the traceback (remember that you have to strip a leading
underscore to go from symify names to C source names).
> Remember that it works fine under windows...
This normally means some NULL pointer access is going on, but
I don't obviously see where this would be in the sources.
Did you recompile FED yourself, or does it also crash with the
version of the executable from my website? If only your
rebuilt version has problems, can you give details of what
djgpp package versions you are using? Otherwise, details about
what DOS version and what type of hardware (in particular your
graphics card) would be useful here.
To get any more accurate info from the traceback you'll need
to build a version with a debug copy of libc, but that means
recompiling at least some of the libc sources on your machine.
It's a shame I can't get my copy to crash in this way!
Shawn Hargreaves.
- Raw text -