g++ (gcc 2.1) on Sun ELC

Article View: gnu.gcc.help

Article #52936

#52936

From: Richard Stallman
Date: Wed, 22 Apr 1992 16:29

9 lines
1056 bytes

If you see part of GCC dump core, there's only one thing you should
do: write a bug report.  See the Bugs chapter in the GCC manual
for how to do this usefully.

To ask "what you are doing wrong" instead of sending a proper bug
report, is inadvisabel for two reasons.  First, you're making a
groundless assumption about the cause of the problem.  Only a proper
investigation can tell determine the cause is.  Second, you are
not helping anyone investigate, thus not helping GCC be fixed.

Technical Details

Message-ID: <9204230029.AA10480@mole.gnu.ai.mit.edu>

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

References: <2811@unisql.UUCP>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 11318c,7eac3aaa4b11348f,start
X-Google-Attributes: gid11318c,public
X-Google-ArrivalTime: 1992-04-22 09:29:24 PST
Newsgroups: gnu.gcc.help
Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!gnu.ai.mit.edu!rms
From: rms@gnu.ai.mit.edu (Richard Stallman)
Subject: g++ (gcc 2.1) on Sun ELC
Message-ID: <9204230029.AA10480@mole.gnu.ai.mit.edu>
Sender: daemon@cis.ohio-state.edu
Organization: GNUs Not Usenet
References: <2811@unisql.UUCP>
Distribution: gnu
Date: Wed, 22 Apr 1992 16:29:24 GMT
Lines: 11

Reply to Parent Message