Path: utzoo!utgpu!water!watmath!uunet!umbc3!alex
From: alex@umbc3.UMD.EDU (Alex S. Crain)
Newsgroups: unix-pc.general
Subject: gnu-cpp + /bin/cc = headache
Message-ID: <1301@umbc3.UMD.EDU>
Date: 27 Oct 88 19:47:32 GMT
Reply-To: alex@umbc3.UMD.EDU (Alex S. Crain)
Organization: University of Maryland, Baltimore County
Lines: 29


	With all these binaries running about, I wanted to make sure that
everyone knew this.

	gnu-cpp irritates a bug in the stock C compiler, causing -g to
produce bogus line #/file name information in the symbol table. The problem
is that gnu-cpp can emit #line directives on consecutive lines, which confuses
the C compiler.

	This bug has no effect on the exectable code, only on the debugging 
information. The fix is simple enough, although if you have gcc its sort of
pointless. Simply chage the printf() statements in the cccp.c file from

	fprintf(outfile,"# line %d, \"%s\"\n", ... )

to

	fprintf(outfile,\n# line %d, \"%s\"\n", ... )
			^
			add a blank line between #line directives.

Note that this is purely from memory, so the exact syntax may differ. There 
are 2 or three instances of this in the cccp.c file.

-- 
					:alex.
					Systems Programmer
nerwin!alex@umbc3.umd.edu		UMBC
alex@umbc3.umd.edu