From: kagel AT quasar DOT bloomberg DOT com
Date: Tue, 17 Dec 1996 16:20:19 -0500
Message-Id: <9612172120.AA14692@quasar.bloomberg.com >
To: boyd AT zansiii DOT millersv DOT edu
Cc: djgpp AT delorie DOT com, budpro AT aol DOT com
In-Reply-To: <5951el$rk3@jake.esu.edu> (boyd@intellmachineslab.millersv.edu)
Subject: Re: Help with debugging
Reply-To: kagel AT dg1 DOT bloomberg DOT com

   Errors-To: postmaster AT ns1
   From: boyd AT intellmachineslab DOT millersv DOT edu (Joshua Boyd)
   Newsgroups: comp.os.msdos.djgpp
   Date: 17 Dec 1996 02:44:37 GMT
   Organization: East Stroudsburg University, Pennsylvania
   Lines: 26
   Nntp-Posting-Host: zansiii.millersv.edu
   X-Newsreader: TIN [version 1.2 PL2]
   Dj-Gateway: from newsgroup comp.os.msdos.djgpp
   Content-Type: text
   Content-Length: 942

   I have been uyseing djgpp for a couple of weeks, and just today a noticed 
   while trying to debug a program that had many errors.  My problem is that 
   the first errors are scrolling off the screen.  I tried several things to 
   try to capture these error messages like gcc temp.c | more and gcc temp.c 
   >c.err where I can the look at c.err in a text editor.  Neither of these 
   work.  I need suggestions on how to see these first errors since allot of 
   the later ones probably stem from the first ones.

   Please CC all replies to my private email budpro AT aol DOT com or 
   boyd AT zansiii DOT millersv DOT edu

Check out the FAQ section 6 (??6.19??) for instructions to use the redir
utility bundled with DJGPP.

-- 
Art S. Kagel, kagel AT quasar DOT bloomberg DOT com

A proverb is no proverb to you 'till life has illustrated it.  -- John Keats