From: ams AT ludd DOT luth DOT se (Martin Str|mberg)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: fsdb crashes post emacs
Date: 1 Aug 1998 18:14:59 GMT
Organization: University of Lulea, Sweden
Lines: 57
Message-ID: <6pvlv3$hep$1@news.luth.se>
References: <Pine DOT LNX DOT 3 DOT 91 DOT 980729114705 DOT 739A-100000 AT aditya DOT unigoa DOT ernet DOT in>
NNTP-Posting-Host: my21.sm.luth.se
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Gurunandan R. Bhat (grbhat AT unigoa DOT ernet DOT in) wrote:
[Klippa, klapp, kluppit backtrace.]

: I then tried to rebuild fsdb with -g for a more meaningful traceback
: using makefile.cws in the directory src/debug/fsdb/ which failed due

Hmm. I wonder what makefile.cws is? Why not use makefile?

: to the presence of a statement
: 
: xorl    %%al, %%al
: 
: in fullscr.c, which I corrected after which fsdb.exe got built. Using

How did you correct it? xorb or %%eax? And where (line number)?

: this "newfsdb myprog.exe" after exiting emacs gives the following
: traceback:
: 
: ------------------------------------------------------------
: Cannot continue from exception, exiting due to signal 0123
: General Protection Fault at eip=00013748
: eax=0000007c ebx=00000004 ecx=fffffffc edx=06d27c0c esi=00000048 edi=0006c306
: ebp=0006c1e8 esp=0006c1e0 
: program=E:\PROGRAMS\ASM\NEWFSDB.EXE
: cs: sel=00a7  base=10000000  limit=0009ffff
: ds: sel=00af  base=10000000  limit=0009ffff
: es: sel=00af  base=10000000  limit=0009ffff
: fs: sel=00cf  base=00016300  limit=000040ff
: gs: sel=00bf  base=00000000  limit=ffffffff
: ss: sel=00af  base=10000000  limit=0009ffff
:  
: Call frame traceback EIPs:
:   0x00013748   _malloc+192
:   0x00013229   _xmalloc+21
:   0x000080a5   _initdisplay+133, line 2147 of fullscr.c
:   0x00008c90   _initialize+364, line 2431 of fullscr.c
:   0x0000aec8   _debugger+52, line 3456 of fullscr.c
:   0x000020af   _main+503, line 139 of ed.c
:   0x00012c5a   ___crt1_startup+454
: ----------------------------------------------------------- 
: 
: I hope that I have done nothing silly.

No, this is a good approach.

Now when you have debug info in fsdb, you could try to run it in
gdb... Or add some "fprintf(stderr, ...)"s just before line 2147 of
fullscr.c to see what it passes to xmalloc.

You could also try fsdb from alpha/9807??/djlsr*.zip and see if that
crashes as well. It doesn't for me.


Penderecki, Polish Requiem,

							MartinS