APP Won't launch in Release settings

Mike24

:mad: Hi out there. I got a problem with an application compiled with Visual NET 2002. My application will not launch when I perform a 'Start without debugging', but will start perfectly if I perform a Start (From the Debug Menu). Once I've performed the start without debugging, I can see that my App is running (an even with 90% of the cpu), but it won't go further ! Same thing if I launch it manually by double-clicking my exe A basic check has been to put a MessageBox at the very first beginning of the program (I can see it when starting From the 'start' menu). This problem only happens with the release configuration of my projects (The debug exe works fine). If anybody could Help, it would be great cyz that stuff is goin to drive me crazy. Thanx in advance Mike.

Navin

The things I would check: 1. Project settings. Are they the same for release as they are for debug? 2. Paths. Perhaps you have relative paths in your code that are breaking when you run from a different spot. 3. Uninitialized variables. Sometimes the debugger will initialize these to 0 and mask out bugs that will manifest in the release builds. "When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity." - Albert Einstein

Tim Smith

Start the application and then use debug/process to attach to it. This will allow you to break the program and see if there is some looping problem. Tim Smith I'm going to patent thought. I have yet to see any prior art.

Maximilien

maybe usefull code put in ASSERT instead of VERIFY ? Max.

Maximilien Lincourt For success one must aquire one's self

Mike24

Thanx for your tip. But I had already tried this, but visual is unable to break into my process. Actually it echoes the following message: Unable to break into the process XXX. Please wait until the debuggee has finished loading and try again

Tim Smith

Does you application use any DLLs that you or a 3rd party wrote? It sounds like on of them might be having problems in their DllMain. Tim Smith I'm going to patent thought. I have yet to see any prior art.

Mike24

Yes indeed. But I got plenty of'em (DX stuff, nvidia cg dlls, my owns...) Gonna have a look at it, thanx