Tracing an applications interaction with OS

Topic

New Reply

Running Win7 64bit SP1 plus updates.

Have a scientific application that calls the system routine cpu_time(time). (Have also tried system_clock and no difference.) With one compiler the timing works with another it doesn’t. Executable of problem app also tested by vendor and it runs fine on their machines using Win7 and Server2008. They sent me their executable and it doesn’t work on my machine. So the app built with the one compiler appears to be interacting or refusing to interact with the call to the system timing routine and this is associated with my machine.

Suggestions on how I might see/study the app’s interaction with the system?

Reply | Quote

Replies

A little more experimentation shows that the app works when I boot into the safe mode.

Anyone with experience on how to identify the conflict? I assume this shows a conflict with a driver or non-OS app?

Reply | Quote

Are these supposedly the same compiler? What compiler?

Joe

--Joe

Reply | Quote

An Intel compiler works. A PGI compiler experiences the problem. As noted above the problem appears to be due to my machine, not the compiler itself.

Reply | Quote

Since it works in Saafe Mode, try the clean boot diagnostic procedure:
http://support.microsoft.com/kb/331796

Jerry

Reply | Quote

Unfortunately Jerry that didn’t do the trick. Thanks for the suggestion.

Reply | Quote

What is the name of the “scientific” application.

Perhaps they are running their app on a clean system and you are not.

Make an imaged backup of your system, then do a clean install. Install the applcation on a clean system with minimal other applications/drivers,
then begin to add others one at a time until you run up to the conflicting application or driver.

Reply | Quote

The app is an R&D one. As I said we exchanged executables for testing.

I was trying to avoid the clean install you suggest since it is extremely time consuming. Are there no other approaches?

Reply | Quote

Unfortunately Jerry that didn’t do the trick. Thanks for the suggestion

What didn’t work? Did the app fail in clean boot mode or did you just run the fixit?

Jerry

Reply | Quote

as you say your friend that sent you the app was using win server 2008 which I think is not supported in standard win 7 64bit maybe this is reason for failure, maybe not.

Reply | Quote

What didn’t work? Did the app fail in clean boot mode or did you just run the fixit?

Jerry

Fixit ran fine but it didn’t fix my problem.

as you say your friend that sent you the app was using win server 2008 which I think is not supported in standard win 7 64bit maybe this is reason for failure, maybe not.

All running on Server2008 says is that the app called cpu_time without any problems. Getting the same answers would be a different issue.

Reply | Quote

Ignore the fixit and follow the diagnostic procedure outlined in the text.

Jerry

Reply | Quote

Ignore the fixit and follow the diagnostic procedure outlined in the text.

Sorry Jerry, I was unclear. I did follow those instructions and still can’t identify the problem source. At some point I’ll just have to bit the bullet and reinstall as Clint suggested.

Reply | Quote