From:	wemccaug AT prairienet DOT org (Wendy E. McCaughrin)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: fsdb and cpp
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 991003122611 DOT 16555R-100000 AT is>
Lines:	29
Message-ID:	<QdvK3.146$_9.52@firefly>
Date:	Tue, 05 Oct 1999 22:47:12 GMT
NNTP-Posting-Host:	192.17.3.4
X-Complaints-To:	newsmgr AT prairienet DOT org
X-Trace:	firefly 939163632 192.17.3.4 (Tue, 05 Oct 1999 17:47:12 CDT)
NNTP-Posting-Date:	Tue, 05 Oct 1999 17:47:12 CDT
Organization:	Prairienet -- Your Community Network for East Central Illinois
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In a previous article, eliz AT is DOT elta DOT co DOT il (Eli Zaretskii) says:

>
>On Fri, 1 Oct 1999, Scott J. McCaughrin wrote:
>
>>  Since I seem to have lost my documentation on 'fsdb':
>>  what do alt-W and alt-S mean in that debugger, and
>>  what do function-keys F3 and F4 do?
>
>The docs are built into FSDB.  Just press F1 inside the debugger and
>read there.

 Thanks, but that was my first solution, and FSDB failed to respond to:
 F1, cntrl-F1, Shift-F1, or Shift-cntrl-F1. Still wondering ...

>
>>  What is the status of 'cpp'? I find that it seems
>>  unable to process conditionals (like #ifndef), with
>>  the result that even simple #include's fail.
>
>You are probably invoking an incorrect program.  Use "gcc -E" instead,
>and you will never have these problems.
>
  I found the bug to be in RHIDE (as others have reported here); gxx
  and gcc handle gpp just fine at command level.

- Raw text -