From:	Bill Currie <bcurrie AT tssc DOT co DOT nz>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: G++ bugs?
Date:	Thu, 04 Dec 1997 08:34:17 +1300
Organization:	Telecommunication Systems Support Centre
Lines:	19
Message-ID:	<3485B439.78B4@tssc.co.nz>
References:	<199712030227 DOT SAA21741 AT adit DOT ap DOT net>
NNTP-Posting-Host:	node106.tssc.co.nz
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Nate Eldredge wrote:
> As somebody said, all you have to do is send them the
> pre-preprocessed source (use `gcc -E' and post its output) and tell them the
> error message you got, what version you use and what platform.

I did something like that with a bug in GAS and I got a patch the next
day.  The more details you can give about a bug, they faster the
maintainers can respond.  What Nate says is perfectly good, but if you
can give minimal code that reproduces the bug, the generated output
(except in this case is was a compiler abort, wasn't it?), and (if
reasonable) the expected output.

Also, even if a bug is already know, having more input examples helps
both nailing down the bug and making sure it stays nailed (the bug
reports can later be used as test cases).

Bill
-- 
Leave others their otherness

- Raw text -