Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <004f01bfe157$4b86e800$46241004@darnold-home.sybase.com>
Reply-To: "Dave Arnold" <avr_fan AT hotmail DOT com>
From: "Dave Arnold" <avr_fan AT nettaxi DOT com>
To: <JSONCRAIG AT aol DOT com>
Cc: <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: gdb running in background
Date: Wed, 28 Jun 2000 16:19:19 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

If you're doing a console style app, couldn't you just use printf?
Another thought is perhaps writing to an error log file and
using tail -f <logfilename>  to act as a sort of console to
view the debug strings as they are written to the log.

If you have more than one executeable accessing the log
at the same time, that might be a little trickier, but it might
be possible based on how you open the file to allow sharing.
I've never done that before.  A thought on that is perhaps
have each process open the log, print, close the log...that
way they're not blocking other processes from writing all
the time.  You'll have to add some checking code to see
if the file is locked on each open attempt and perhaps a wait
until it's free.

/dAVe

-----Original Message-----
From: JSONCRAIG AT aol DOT com <JSONCRAIG AT aol DOT com>
To: cygwin AT sourceware DOT cygnus DOT com <cygwin AT sourceware DOT cygnus DOT com>
Date: Wednesday, June 28, 2000 10:22 AM
Subject: gdb running in background


>Is there some way that one can run gdb so that it will just sit there, and
>display any OutputDebugString() messages that are called?  I know gdb will
>display them, if you are currently debugging that program, but this seems
>kind of clunky if I just want to see debug updates, especially if I have
more
>than one executable.
>
>Any help is appreciated,
>Jason Craig
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com