Windows TRACE message

Windows TRACE message

[Rui-Tao Dong]

Is there a way to re-direct windows TRACE message to stderr under cygwin?

-- 
Regards,

			Rui-Tao (x679)


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

Re: Windows TRACE message

[Mumit Khan]

On 8 Jul 1999, Rui-Tao Dong wrote:

> 
> Is there a way to re-direct windows TRACE message to stderr under cygwin?
> 

What're windows TRACE messages?

Regards,
Mumit



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

Re: Windows TRACE message

[Rui-Tao Dong]

>>>>> "Mumit" == Mumit Khan <khan@xraylith.wisc.EDU> writes:

 >> Is there a way to re-direct windows TRACE message to stderr under
 >> cygwin?
 >> 

 Mumit> What're windows TRACE messages?

I mean messages shows up in VC studio's message window (produced by
TRACE macro?).


-- 
Regards,

			Rui-Tao (x679)


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

Re: Windows TRACE message

[Mumit Khan]

Rui-Tao Dong <rdong@newport.com> writes:
> 
> >>>>> "Mumit" == Mumit Khan <khan@xraylith.wisc.EDU> writes:
> 
>  >> Is there a way to re-direct windows TRACE message to stderr under
>  >> cygwin?
>  >> 
> 
>  Mumit> What're windows TRACE messages?
> 
> I mean messages shows up in VC studio's message window (produced by
> TRACE macro?).
> 

TRACE is not part of Win32 API, but rather part of MFC. However, it
looks like it's a "printf" style interface, so for a console-mode
program, a trivial implementation may look like the following:

  #include <stdio.h>

  #define TRACE printf
  int
  main ()
  {
    TRACE ("Entering %s\n", __PRETTY_FUNCTION__);
    TRACE ("Leaving %s\n", __PRETTY_FUNCTION__);
    return 0;
  }


$ gcc -o foo-test foo-test.c
$ ./foo-test
Entering main
Leaving main

Of course, a reasonable implementation would something much more complicated
to avoid code and runtime overhead when TRACE is turned off.

Hint: define TRACE in terms of a function taking variable number of
arguments and there use ANSI vfprintf routine to do the printing if
tracing is enabled or just return.

A win32 implementation should also check if it's GUI app; if so, open
a new console (AllocConsole and so on) and write to the new console
(or open a window with a text widget and send text to it).

Feel free to innovate. It really isn't a Cygwin issue of course.

Regards,
Mumit


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

Re: Windows TRACE message

[Lars Gregersen]

> >  Mumit> What're windows TRACE messages?
> > 
> > I mean messages shows up in VC studio's message window (produced by
> > TRACE macro?).
> > 
> 
> TRACE is not part of Win32 API, but rather part of MFC. However, it
> looks like it's a "printf" style interface, so for a console-mode
> program, a trivial implementation may look like the following:

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

  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

Re: Windows TRACE message

[Mumit Khan]

"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
> 

Lars,

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
everything there. Very simple, and you can use iostream style
formatting.

  debugout << __FILE__ << ": " __LINE << ": " 
    << "error message here ...." << endl;
  
The default class simply dumps to cerr.

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.

The trick is to make sure that the global constructor for the 
debug stream is initialized before anything else, but right
after iostreams is initialized.

Regards,
Mumit


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

Re: Windows TRACE message

[Lars Gregersen]

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

Re: Windows TRACE message

[Jonathan Pryor]

Mumit,

kenneth Brubaker has released something similar to your 
"debugout" class, and he outlined it in the May 1999 issue 
of _C++ Report_.

The source is available as two listings; the source is at:

< http://archive.creport.com/9905/html/from_pages/code.shtml >

It's by no means perfect, but it provides printf()-style
functions  (called dprintf()) and IO-streams classes 
(through the `dout' class) that send output to the 
Windows' OutputDebugStream API, which can be captured with
the sysinternals' program previously mentioned on the list.

The original code, unfortunately, is rather MSVC-specific,
as it requires the newer template-based IO-streams library,
plus the requirement of the OutputDebugString API.

However, I've been hacking on the source to allow 
redirection to stdout/stderr (or any other FILE*), and it
currently works on Linux without too many problems.  I'll
probably put the source out after I deal with some 
multi-threading initialization issues (which consist of
a total lack of threading support).

 - Jon


----- Original Message ----- 
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: <lg@kt.dtu.dk>
Cc: <cygwin@sourceware.cygnus.com>
Sent: Friday, July 09, 1999 2:47 AM
Subject: Re: Windows TRACE message 


> "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
> > 
> 
> Lars,
> 
> 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
> everything there. Very simple, and you can use iostream style
> formatting.
> 
>   debugout << __FILE__ << ": " __LINE << ": " 
>     << "error message here ...." << endl;
>   
> The default class simply dumps to cerr.
> 
> 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.
> 
> The trick is to make sure that the global constructor for the 
> debug stream is initialized before anything else, but right
> after iostreams is initialized.
> 
> Regards,
> Mumit
> 
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 


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

Re: Windows TRACE message

[Lars Gregersen]

> >  Mumit> What're windows TRACE messages?
> > 
> > I mean messages shows up in VC studio's message window (produced by
> > TRACE macro?).
> > 
> 
> TRACE is not part of Win32 API, but rather part of MFC. However, it
> looks like it's a "printf" style interface, so for a console-mode
> program, a trivial implementation may look like the following:

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

  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

Re: Windows TRACE message

[Mumit Khan]

Rui-Tao Dong <rdong@newport.com> writes:
> 
> >>>>> "Mumit" == Mumit Khan <khan@xraylith.wisc.EDU> writes:
> 
>  >> Is there a way to re-direct windows TRACE message to stderr under
>  >> cygwin?
>  >> 
> 
>  Mumit> What're windows TRACE messages?
> 
> I mean messages shows up in VC studio's message window (produced by
> TRACE macro?).
> 

TRACE is not part of Win32 API, but rather part of MFC. However, it
looks like it's a "printf" style interface, so for a console-mode
program, a trivial implementation may look like the following:

  #include <stdio.h>

  #define TRACE printf
  int
  main ()
  {
    TRACE ("Entering %s\n", __PRETTY_FUNCTION__);
    TRACE ("Leaving %s\n", __PRETTY_FUNCTION__);
    return 0;
  }


$ gcc -o foo-test foo-test.c
$ ./foo-test
Entering main
Leaving main

Of course, a reasonable implementation would something much more complicated
to avoid code and runtime overhead when TRACE is turned off.

Hint: define TRACE in terms of a function taking variable number of
arguments and there use ANSI vfprintf routine to do the printing if
tracing is enabled or just return.

A win32 implementation should also check if it's GUI app; if so, open
a new console (AllocConsole and so on) and write to the new console
(or open a window with a text widget and send text to it).

Feel free to innovate. It really isn't a Cygwin issue of course.

Regards,
Mumit


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

Re: Windows TRACE message

[Jonathan Pryor]

Mumit,

kenneth Brubaker has released something similar to your 
"debugout" class, and he outlined it in the May 1999 issue 
of _C++ Report_.

The source is available as two listings; the source is at:

< http://archive.creport.com/9905/html/from_pages/code.shtml >

It's by no means perfect, but it provides printf()-style
functions  (called dprintf()) and IO-streams classes 
(through the `dout' class) that send output to the 
Windows' OutputDebugStream API, which can be captured with
the sysinternals' program previously mentioned on the list.

The original code, unfortunately, is rather MSVC-specific,
as it requires the newer template-based IO-streams library,
plus the requirement of the OutputDebugString API.

However, I've been hacking on the source to allow 
redirection to stdout/stderr (or any other FILE*), and it
currently works on Linux without too many problems.  I'll
probably put the source out after I deal with some 
multi-threading initialization issues (which consist of
a total lack of threading support).

 - Jon


----- Original Message ----- 
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: <lg@kt.dtu.dk>
Cc: <cygwin@sourceware.cygnus.com>
Sent: Friday, July 09, 1999 2:47 AM
Subject: Re: Windows TRACE message 


> "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
> > 
> 
> Lars,
> 
> 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
> everything there. Very simple, and you can use iostream style
> formatting.
> 
>   debugout << __FILE__ << ": " __LINE << ": " 
>     << "error message here ...." << endl;
>   
> The default class simply dumps to cerr.
> 
> 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.
> 
> The trick is to make sure that the global constructor for the 
> debug stream is initialized before anything else, but right
> after iostreams is initialized.
> 
> Regards,
> Mumit
> 
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 


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

Re: Windows TRACE message

[Lars Gregersen]

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

Re: Windows TRACE message

[Mumit Khan]

On 8 Jul 1999, Rui-Tao Dong wrote:

> 
> Is there a way to re-direct windows TRACE message to stderr under cygwin?
> 

What're windows TRACE messages?

Regards,
Mumit



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

Windows TRACE message

[Rui-Tao Dong]

Is there a way to re-direct windows TRACE message to stderr under cygwin?

-- 
Regards,

			Rui-Tao (x679)


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

Re: Windows TRACE message

[Rui-Tao Dong]

>>>>> "Mumit" == Mumit Khan <khan@xraylith.wisc.EDU> writes:

 >> Is there a way to re-direct windows TRACE message to stderr under
 >> cygwin?
 >> 

 Mumit> What're windows TRACE messages?

I mean messages shows up in VC studio's message window (produced by
TRACE macro?).


-- 
Regards,

			Rui-Tao (x679)


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

Re: Windows TRACE message

[Mumit Khan]

"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
> 

Lars,

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
everything there. Very simple, and you can use iostream style
formatting.

  debugout << __FILE__ << ": " __LINE << ": " 
    << "error message here ...." << endl;
  
The default class simply dumps to cerr.

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.

The trick is to make sure that the global constructor for the 
debug stream is initialized before anything else, but right
after iostreams is initialized.

Regards,
Mumit


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

Re: Windows TRACE message

[Mumit Khan]

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

Re: Windows TRACE message

[Rui-Tao Dong]

>>>>> "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.

-- 
Regards,

			Rui-Tao (x679)


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

Re: Windows TRACE message

[Mumit Khan]

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

Re: Windows TRACE message

[Rui-Tao Dong]

>>>>> "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.

-- 
Regards,

			Rui-Tao (x679)


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