[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tricks for Windows coding and win version status

From: Alberto Curro
Subject: Re: Tricks for Windows coding and win version status
Date: Sat, 10 Aug 2002 23:01:35 +0200

Hash: SHA1

> Then the most likely thing is that the application indeed does exit
> cleanly. Most likely cause is that an exception is thrown, its caught by a
> handler that writes it to stdout and then exits.
> In linux this message would be visible, but that is not the case for
> Windows.
> There are several ways you can make the message visible. One is to run the
> application from the command prompt, piping it to a file:
> pingus.exe > output.txt
> Other way is to create a CL_ConsoleWindow and then just before pingus
> exits, call the CL_ConsoleWindow::display_close_message(). This method is
> the nicest one for a Windows developer since it creates a console window
> where you can see things written as they happen. I recommend you only
> create and use the console window in debug builds, eg. by putting it into
> #ifdef DEBUG clauses.

  Okay, I will try it and comment you something in the next (few, though) 

> >   Referring to debugging the application, I can place  breakpoints (of
> > course, I'm in debug mode) but when the application reaches the
> > breakpoint, the only window I can see for debug is CPU Window. I cannot
> > place watches, or inspect code, nothing...
> Hmm, that sounds strange. Dont know what could be causing that.

  I don't know, too. I'm thinking about recommending Visual C++ for the most 
buggy development IDE + compiler of the year (if not the entire century! :)). 
given my experience with it, both at work and personal, I can say now ... I 
prefer emacs + gcc !!!!


    Alberto curro

Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see


reply via email to

[Prev in Thread] Current Thread [Next in Thread]