runtime error

[Martinakos]

Hi,

I have a visual studio project that builds well but when I run it I get a pop up with the message
“The application was unable to start correctly (0xc000007b). Click Ok to close the application” and the output window says “The program '[1184] LiveDriverApp.exe: Native' has exited with code -1073741701 (0xc000007b)". No other message that can give more information, before that there was just loading of dlls.

Any ideas why could this happen? How do I debug this?

thanks
Martinakos

[Martinakos]

Oh! btw, I forgot.

Window 7, and a 32bit build.

[Paul McKenzie]

Hi,

I have a visual studio project that builds well

Which really doesn't mean anything. All that means is that your program has no syntax errors. It has no bearing on whether the program will run successfully.

“The application was unable to start correctly (0xc000007b). Click Ok to close the application” and the output window says “The program '[1184] LiveDriverApp.exe: Native' has exited with code -1073741701 (0xc000007b)". No other message that can give more information, before that there was just loading of dlls.

Any ideas why could this happen?

Your pogram has a bug

How do I debug this?

Start your debugger and debug your program. Or more than likely, you are attempting to load DLL's that are incompatible with the system you're running (32/64 bit conflict).

Regards,

Paul McKenzie

[Martinakos]

Hi Paul ,


Thanks for your reply.
I can't debug anything, I press F5 and this pop out window appears before arriving to the main().
I guess it may be dlls. I wonder if there is an effective way of debuging this.

Regards,
Martin.

[Paul McKenzie]

Hi Paul ,


Thanks for your reply.
I can't debug anything, I press F5 and this pop out window appears before arriving to the main().
I guess it may be dlls. I wonder if there is an effective way of debuging this.

Regards,
Martin.

If you're running 64-bit Windows 7, you have to make sure that your 32-bit app loads the 32-bit versions of the DLLs it needs.

Use the Dependency Walker program to see exactly what DLL's your application needs. If the names of the DLL's conflict with the names of the DLL's that happen to be 64-bit, then that is one of many reasons why your app fails to start.

Also, use Process Explorer from sysinternals.com. When you start your app, with Process Explorer you can see the DLL's and the full path of where those DLL's are being found by the system. If the DLL is in the path where the 64-bit version of the DLL is located, then again, this is not correct.

Regards,

Paul McKenzie