delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2001/06/21/08:10:16

From: invalid AT erehwon DOT invalid (Graaagh the Mighty)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Info.
Organization: Low Charisma Anonymous
Message-ID: <3b31a206.174446194@news.primus.ca>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010619120836 DOT 7390X-100000 AT is>
X-Newsreader: Forte Free Agent 1.11/32.235
Lines: 44
Date: Thu, 21 Jun 2001 07:32:55 GMT
NNTP-Posting-Host: 207.176.153.34
X-Complaints-To: news AT primus DOT ca
X-Trace: news2.tor.primus.ca 993108733 207.176.153.34 (Thu, 21 Jun 2001 03:32:13 EDT)
NNTP-Posting-Date: Thu, 21 Jun 2001 03:32:13 EDT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

On Tue, 19 Jun 2001 12:15:55 +0300 (IDT), Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> sat on a tribble, which squeaked:

>Please post the entire crash message here.  Please also tell what command 
>line did you use to invoke Info.

I don't have it here and I'm not about to reboot *twice* to get it.
Suffice it to say it was a sigsegv. The command line: "info", plain
and simple. "info libc a fopen" segfaulted, so I tried plain "info",
which died identically.

>FWIW, this is the first segfault report about Info 4.0, IIRC.  This is 
>probably something specific to your system, or some very subtle bug that 
>is triggered for something on your system.

There's nothing unusual about my system. Especially under pure DOS,
there's not much variation to be had in the configuration. Swap size
under cwsdpmi is about it. Of course info has some kind of search path
for its files, too, but it should complain gracefully instead of crash
if this is fouled up. Besides, it's the same under Windows, where info
works. Most likely, it's a heisenbug, depending on uninitialized
memory. Certainly it will behave differently then under DOS and
Windows, and may depend under DOS upon what kinds of device drivers
and stuff are used.

>Some DOS systems might have problems with the way Info switches the 
>display to 40-line mode.  Try setting INFO_LINES=50 in the environment, 
>before running Info, and see if that helps.

Why would that be? The VGA screen modes available with one graphics
card are the same as those available with any other. Info doesn't try
to use a non-VGA mode does it? If it does, doesn't it test for success
and handle failure gracefully?

>Btw, do you still have an outdated DJGPP installation?  Maybe that is 
>your problem, if you do.

This problem appeared with an *upgrade* to the version of info on my
system.
-- 
Bill Gates: "No computer will ever need more than 640K of RAM." -- 1980
"There's nobody getting rich writing software that I know of." -- 1980
"This antitrust thing will blow over." -- 1998
Combine neo, an underscore, and one thousand sixty-one to make my hotmail addy.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019