public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: Rui-Tao Dong <rdong@newport.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Windows TRACE message
Date: Sat, 31 Jul 1999 18:34:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.96.990711143236.29235C-100000@mercury.xraylith.wisc.edu> (raw)
Message-ID: <19990731183400.l0zdiSrkmzOOJu69cgT_grh_EMYobHP_Za8UgLDKHrA@z> (raw)
In-Reply-To: <v5d7y1baxl.fsf@Phantom.newport.com>

On 9 Jul 1999, Rui-Tao Dong wrote:

> 
> >>>>> "Mumit" == Mumit Khan <khan@xraylith.wisc.EDU> writes:
> 
> 	----------------------------------------
> 
>  Mumit> TRACE is not part of Win32 API, but rather part of
>  Mumit> MFC. However, it looks like it's a "printf" style interface,
>  Mumit> so for a console-mode program, a trivial implementation may
>  Mumit> look like the following:
> 
> I should have explained this better.  I am trying to get these
> messages from existing applications.  I did a Deja search and found a
> couple of Window's ways of doing that (hacking dll to re-direct it to
> a window).  I normally start applications from a cygwin tcsh (in an
> XEmacs buffer displaying to a VNC server on a Linux machine and viewed
> back on NT, if you really want to know :-).  It would be nice if I can
> catch these messages in the buffer.  Re-direct to a file is OK, too.
> Because I can just do a tail -f in another buffer.
> 

Sorry, I don't know anything about this. This is not really a Cygwin 
issue per se from your description, and one of the windows newsgroups 
may be more appropriate/helpful.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~1999-07-31 18:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-09 17:38 Rui-Tao Dong
1999-07-11 12:34 ` Mumit Khan [this message]
1999-07-31 18:34   ` Mumit Khan
1999-07-31 18:34 ` Rui-Tao Dong
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=Pine.LNX.3.96.990711143236.29235C-100000@mercury.xraylith.wisc.edu \
    --to=khan@xraylith.wisc.edu \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=rdong@newport.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).