Xref:	news2.mv.net comp.os.msdos.djgpp:1445
From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: djgpp v2 patches, bug reports, questions, suggestions (long)
Date:	Sat, 24 Feb 1996 16:40:30 CST
Organization:	Rice University, Houston, Texas
Lines:	42
Message-ID:	<312f93de.sandmann@clio.rice.edu>
References:	<312FC387 DOT 7266 AT jk DOT uni-linz DOT ac DOT at>
Reply-To:	sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host:	clio.rice.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

> Markus F.X.J. Oberhumer <markus DOT oberhumer AT jk DOT uni-linz DOT ac DOT at> writes:
> - where exactly should I send (longer) library patches

Zip em up, and ftp them to ftp.delorie.com, put them in the incoming, and
send dj AT delorie DOT com a note.

> - where exactly should I send (longer) patches regarding djgpp specific 
>   problems of the GNU utilities or gcc

It depends on if it's a libc problem, a configuration problem, or a FSF bug.
The first two go to the DJGPP developers (djgpp-workers AT delorie DOT com), the
last goes to the FSF.  See http://www.delorie.com for a page to report
short bugs, join mailing lists, search mailing list archives, etc.

> I don't want to send (possibly annoying) personal mail for
> every trivial patch/bug I've found, but I DO want to send it 
> if I think it should be fixed or noticed.

Send the mail.  At best it surfaces an unknown problem, at worse it gets
deleted and ignored.  Thanks for the input!

> errno should be set, sigaction() does not fail, signal()/sigaction() mismatch

None of these sorts of bugs surprise me, since I wrote signal in an evening
on the basis of what I needed instead of looking at documentation, and DJ
wrote the POSIX signal stuff, and we never reviewed it/compared notes.

> and installs a protected mode interrupt handler for int 9.  serious troubles
> in a Windows 3.1 DOS box ... the keyboard doesn't respond any more 
> - even the Windows hot keys are dead - and I have to do a cold boot.

This sounds like the Windows loses hardware interrupts bug.  If you
mess with the interrupt flag, cli/sti, or dpmi interrupt clear functions,
Windows sometimes gets confused and leaves interrupts disabled.  It looks
like a Win bug to us, but maybe something in exceptn.S isn't quite right.

> Why do we have that much troubles with djgpp, MikMod and sb_lib
> also don't work in a DOS box ? 

Some of these are issues with GCC not knowing directly about interrupt
routines, others with allowing virtual memory and hardware interrupts.
I'd be happy to try and help you work out the problems.

- Raw text -