Xref:	news-dnh.mv.net comp.os.msdos.djgpp:2050
Path:	news-dnh.mv.net!mv!news.sprintlink.net!in1.uu.net!news1.digital.com!pa.dec.com!depot.mro.dec.com!mrnews.mro.dec.com!news
From:	Damien Gardner <dgardner>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Problem with Texinfo and QDPMI
Date:	15 Sep 1995 08:56:31 GMT
Organization:	Digital Equipment International B.V.
Lines:	75
References:	<DEuuu1 DOT F6x AT jade DOT mv DOT net>
Nntp-Posting-Host:	16.183.160.168
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
>
>On Tue, 12 Sep 1995 dgardner AT mcsilo DOT ilo DOT dec DOT com wrote:
>
>> PROBLEM: INFO.EXE (from txi360b-beta3.zip) crashes immediately when QDPMI
>> is loaded and is fine when I type CWSDPMI before running it (even when
>> QDPMI has been loaded on boot-up).  Each time I go to run it, I have to
>> reload CWSDPMI.  Everything else seems to work okay (although I haven't
>> tried much as I've only used v2b3 for a few hours so far.)
>
>I work under QDPMI all the time, including with Texinfo 3.6 (for whose 
>port to DJGPP I am responsible), and never had any problems.  There are 
>three things I can suggest:
>
>	1) Get the latest patch #3 of QEMM 7.5 from the Quarterdeck's ftp 
>site (ftp://qdeck.com/pub/qemm/patch/qpat3.exe), which solved some 
>problems (in particular, the DJGPP debuggers would crash under previous 
>versions of QDPMI).
>

I got the patch but then found out that the QEMM386.SYS file was up to 
date and the patch was unnecessary.  Just to cover all the angles, though,
I applied the patch to a backup of QEMM and there was no improvement.

>	2) If that won't help, it can be that the problem is with the 
>setup of your system, either with your VGA card or some resident software 
>(TSR or device driver).  Try unloading some of these resident programs 
>and/or load the UNIVBE program which solves many problems with VGA 
>cards.  Also, if you set the INFO_COLORS or INFO_LINES variables, try 
>without them.
>

I don't have an SVGA card just an old VGA in an old 386dx33+387 that has
never caused problems with anything before.

>	3) It also can be that there is a genuine bug in the ported Info 
>program (it's beta, after all).  So if nothing else helps, please post 
>the stack dump which is printed when the program crashes, and tell some 
>more details about the crash.  You can even download the source 
>distribution, compile the program and run SYMIFY on the stack dump; you 
>will then know exactly which source line in which source file caused the 
>crash.

THIS JUST IN: The bug has nothing whatsoever to do with QEMM or any TSRs.
I have booted up with only HIMEM.SYS (and I mean *only* HIMEM.SYS!) and
still have problems.

I got the source code and for texinfo and ran the makefile (with no changes)
and it built INFO.EXE without even a warning message.  I left it in the
c:/dj2b3/gnu/texinfo3.6/info directory.  This build of info.exe seems a
little different to the one in the BIN directory but it contains the
symbols that make symify useful.

The weird stuff is now beginning to happen!!  I haven't tested all the
possibilities so I won't go into the details just yet but my suspicions
are tending towards a bug in crt0.o or something that it calls and not
in texinfo.  I'll throw some time at the problem over the weekend and
see if I can come up with anything useful.

I have real serious problems with gdb sometimes (it runs but as soon as
I hit a key, the program crashes and hangs the machine so I can't even
run symify on it.)  I'll get the source for this too and see if I can
find out what's wrong.

I'll keep you posted.


TTFN,
Damien.

-- 
Could anyone tell me why my .signature doesn't appear when I do this?

#include ".signature"

- Raw text -