Date: Mon, 10 Jun 1996 12:05:22 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: j DOT aldrich6 AT genie DOT com
Cc: djgpp AT delorie DOT com
Subject: Re: Printer Error (was Re: Listing
In-Reply-To: <199606092215.AA004898549@relay1.geis.com>
Message-Id: <Pine.SUN.3.91.960610120154.2931C-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Sun, 9 Jun 1996 j DOT aldrich6 AT genie DOT com wrote:

> encountered another problem.  If I told the program to output to stdprn
> when my printer was not turned on, then the first call to fprintf using
> stdprn would cause a SIGSEGV.
[snip]
> --- Under DOS w/CWSDPMI ---
> 
> C:\CPROGS>test2
> Exiting due to signal SIGSEGV
> Page fault at eip=00006168, error=0006
> eax=00000000 ebx=ffffffff ecx=00007f14 edx=00000054 esi=00000000 edi=00007f14
> ebp=000462a4 esp=00046294 cs=00e7 ds=00ef es=00ef fs=00cf gs=00ff ss=00ef
> Call frame traceback EIPs:
>   0x00006168  __flsbuf+60
>   0x000041da  __doprnt+170
>   0x00001f2d  _fprintf+105
>   0x00001597  _main+23, line 9 of test2.c
>   0x00001aeb  ___crt1_startup+115

This seems to be something VERY DPMI-server-dependent.  I get the above 
crash with CWSDPMI, Win3.1 prints "Error writing to printer.", but 
QDPMI prints (tadam!) "Printer is ok.".

Charles?