Reporting bugs

Article View: gnu.gcc.help

Article #52874

#52874

From: Richard Stallman
Date: Sat, 25 Apr 1992 10:10

11 lines
1050 bytes

I'd like everyone to know that it is *not essential*
to find a simple test case in order to send a bug report.
A complex test case is almost as good, as long as you point out
where the error is.

If you do have time to simplify the test case, that is helpful.
But if you don't have time for that, please send a bug report anyway,
with any test case that "works" to reproduce the bug.

For more info, please see the chapter on Bugs in the GCC manual.
All GCC users ought to read it.

Technical Details

Message-ID: <9204251810.AA18985@mole.gnu.ai.mit.edu>

Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!gnu.ai.mit.edu!rms

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 11318c,c7923af4523a440c,start
X-Google-Attributes: gid11318c,public
X-Google-ArrivalTime: 1992-04-25 03:10:03 PST
Newsgroups: gnu.gcc.help
Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!gnu.ai.mit.edu!rms
From: rms@gnu.ai.mit.edu (Richard Stallman)
Subject: Reporting bugs
Message-ID: <9204251810.AA18985@mole.gnu.ai.mit.edu>
Sender: daemon@cis.ohio-state.edu
Organization: GNUs Not Usenet
Distribution: gnu
Date: Sat, 25 Apr 1992 10:10:03 GMT
Lines: 11