Mail Archives: djgpp/1996/10/08/14:56:22
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
>....
>However, without a full traceback, it is impossible to say what exactly
>goes wrong. For all I know, it might be that the program passes a null
>pointer to `memcpy' and is killed by CWSDPMI's null pointer protection,
>whereby on NT it manages to get away with it.
Thanks to all who replied. Here is the complete traceback:
init...Exiting due to signal SIGSEGV
Page fault at eip=0000c695, error=0006
eax=00000000 ebx=00000000 ecx=00000046 edx=00058000 esi=00063c00
edi=00000014
ebp=00053cec esp=00053ce0 cs=00a7 ds=00af es=00af fs=008f gs=00bf ss=00af
Call frame traceback EIPs:
0x0000c695 ___dj_movedata+33
0x0000301c _wnoutrefresh+476, line 196 of refresh.c
0x00002e29 _wrefresh+89, line 133 of refresh.c
0x00001669 _init_curses_disp+217, line 29 of test_cur.c
0x00001707 _main+23, line 42 of test_cur.c
0x00008497 ___crt1_startup+115
C:\APPLIC>symify -o res.txt test_cur.exe
Ronen
ronen AT friendly DOT co DOT il
- Raw text -