Assertions not showing, it makes difficult to work like this

[thorlak]

Hi everybody!

I have recently installed Visual Studio 2008 and started programming a C++ application.
I have some assertions in my code, but none of them pops up the typical "error window" when the execution of the application fails.

The output prompts this:

The thread 'Win32 Thread' (0xcd4) has exited with code 3 (0x3).
The program '[2372] MyApp.exe: Native' has exited with code 3 (0x3).

When this happens I do not have the option to debug and breakpoint the source code. It just crashes and I don't know where it crashed....

I don't understand it, has someone experienced this before??
How can I fix it? I would like to see where the program crashes and see the pop up assertion window.

Can someone help me please?

PS: I have Windows XP SP3 and i'm using VS2008 express edition.

[GCDEF]

An ASSERT has to get hit before it'll stop the program. A crash and an ASSERT aren't the same thing.

I'd be putting breakpoints in various parts of the program and see how far you get. Try to narrow it down that way.

[thorlak]

Hi GCDEF,

The thing is that i am working with a group of people. We use the same code, with the same assertions, etc. And to my friends the assertions pop up windows are being shown, but when it comes to me the program just exits/crashes with code 3 (0x3).

I've also tried using breakpoints just before an assert and when i hit next step, the program crashes at the assert with the same code.

I don't know what to do

[GCDEF]

You are doing a debug build right - not a release build with debug information?

[joe_stoll]

add another beak point some where else,why not add a break point in all of your functions/classes and as you are figuring out which ones remove the ones that are not causing the assertion and watch certain variables. or put TRACE( "code made it to nameofclass \n" );@ the top of each class in its member body and watch your debug window and last class accessed will appear near end of statements