From: "Lars Gregersen" <lg@popeye.kt.dtu.dk>
To: cygwin@sourceware.cygnus.com
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Windows TRACE message
Date: Sat, 31 Jul 1999 18:34:00 -0000 [thread overview]
Message-ID: <5EC0834391@popeye.kt.dtu.dk> (raw)
Message-ID: <19990731183400.ChEEdtm_TeigrgTlbdbQ--hr-tydgSD4lFm0vuI27i4@z> (raw)
In-Reply-To: <199907090647.BAA29870@mercury.xraylith.wisc.edu>
To: lg@kt.dtu.dk
Copies to: cygwin@sourceware.cygnus.com
Subject: Re: Windows TRACE message
Date sent: Fri, 09 Jul 1999 01:47:41 -0500
From: Mumit Khan <khan@xraylith.wisc.EDU>
> "Lars Gregersen" <lg@popeye.kt.dtu.dk> writes:
> >
> > I prefer to use the API function OutputDebugString. It isn't as
> > powerful as the printf type of commands, but it sends a string to a
> > seperate debug window. This also has the great effect that I'f you're
> > testing multiple programmes at the same time you get the output in order
> > in the same window. It works for GUI and console programmes.
> >
> > You can get a debug string viewer (for free) at www.sysinternals.com
> Thanks for the very useful pointer.
>
> I tend to use a debugging stream (most of my code is C++) that has
> a subclass for win32 that opens a scrolled window and just dumps
This looks very much like the OutputDebugString method. Of course the
sysinternals prorgamme has things such as time, filters, remote
debugging that sometimes comes in handy.
I also use this for Matlab programming where I can check out my (very
simple) socket pramming when communicating between Matlab and C++
programmes.
In any event, all the tools as sysinternals.com are top quality and
very useful - and they're free. The only programme of theirs I
haven't tested is their Blue Screen of Death Screensaver ;-)
> everything there. Very simple, and you can use iostream style
> formatting.
This I really miss for the OutputDebugString method!
> One of these days I'll clean up the copyright and release it. it's
> part of a commercial package, but since I own it, I can probably
> convince our commercial arm to make it freely available.
Like the rest of the things you're providing us with I will be
looking very much forward to this.
Regards
Lars
---------------------------------------------------------------------
Lars Gregersen Telephone no.: +45 45 25 28 08
Technical University of Denmark Fax no. : +45 45 88 22 58
Department of Chemical Engineering E-mail : lg@kt.dtu.dk
Bygning 229
DK-2800 Lyngby
Denmark
---------------------------------------------------------------------
Homepage: http://www.gbar.dtu.dk/~matlg/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-07-31 18:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-08 14:53 Rui-Tao Dong
1999-07-08 16:12 ` Mumit Khan
1999-07-08 16:17 ` Rui-Tao Dong
1999-07-08 22:13 ` Mumit Khan
1999-07-08 23:28 ` Lars Gregersen
1999-07-08 23:47 ` Mumit Khan
1999-07-08 23:56 ` Lars Gregersen [this message]
1999-07-31 18:34 ` Lars Gregersen
1999-07-12 5:52 ` Jonathan Pryor
1999-07-31 18:34 ` Jonathan Pryor
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` Lars Gregersen
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` Rui-Tao Dong
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` Rui-Tao Dong
1999-07-09 17:38 Rui-Tao Dong
1999-07-11 12:34 ` Mumit Khan
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` Rui-Tao Dong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5EC0834391@popeye.kt.dtu.dk \
--to=lg@popeye.kt.dtu.dk \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).