From:	ams AT ludd DOT luth DOT se (Martin Str|mberg)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: fsdb crashes post emacs
Date:	4 Aug 1998 17:24:23 GMT
Organization:	University of Lulea, Sweden
Lines:	29
Message-ID:	<6q7g47$n5m$1@news.luth.se>
References:	<Pine DOT LNX DOT 3 DOT 91 DOT 980804051135 DOT 5934A-100000 AT aditya DOT unigoa DOT ernet DOT in>
NNTP-Posting-Host:	queeg.ludd.luth.se
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Gurunandan R. Bhat (grbhat AT unigoa DOT ernet DOT in) wrote:
: > How did you correct it? xorb or %%eax? And where (line number)?
: 
: Actually there is only one occurence of this staement in fullscr.c and 
: a simple search will get you a line number. Unfortunately, the machine 

Actually not where I looked; there's one xorb and one xorl; that's why
I asked. This is probably because I was looking in an alpha of djlsr.

: I have now built fsdb by linking in malloc by hand and with the -g option.
: I now have some understanding of what is happening. As Eli correctly
: reasoned (without the benefit of an unstripped malloc and -g!!) one member
: of the linked list maintained by malloc/free points somewhere in the 
: region of Mars.  In terms of malloc's variables,
: 
: op->ov_next = garbage 
: 
: so that when this member is handed out to the application dereferencing 
: it causes the crash. I am currently using (learning) gdb to go through the 
: code and will report progress if any.

Perhaps you should try alpha/*/djlsr*.zip and see if you have the same
problem? As I mentioned there have been changes, although I don't know
if they change anything for you.


Hungness, Virtual Symphony No. 1,

							MartinS

- Raw text -