How can I investigate the source of an Access Violation that occurs on launching the app?

As you say it is a Windows application. Then, any issues with startup, I have found ADPlus very useful EDIT 2: You may also check User Mode Process Dumper if ADPlus does not apply.

As you say it is a Windows application. Then, any issues with startup, I have found ADPlus very useful. EDIT 2: You may also check User Mode Process Dumper if ADPlus does not apply.

Do not use ADPlus in the following situations: If you must troubleshoot a program or process that quits unexpectedly during startup. You can only use ADPlus for processes that start successfully. To troubleshoot processes that quit unexpectedly during startup, User Mode Process Dump may be a better solution.

For more information about User Mode Process Dump, click the following article number to view the article in the Microsoft Knowledge Base: 253066 ... Should I try this "User Mode Process Dump"? – EKI Nov 1 '10 at 13:45 Oops!. Your comment and my REEDIT crossed each other.

Yes, that is true. You will have to give it a try since it is giving 'access violation' rather than unexpected termination. Unexpected termination is different from access violation.

– Chubsdad Nov 1 '10 at 13:47 You can use process dumper for ANY process exit. – Steve Townsend Nov 1 '10 at 13:57 I used the User Mode Process Dump and opened it with WinDbg and this is the info that it has in it: Loading unloaded module list . This dump file has an exception of interest stored in it.

The stored exception information can be accessed via .ecxr.(5f8.Cc): Access violation - code c0000005 (first/second chance not available) eax=0023feb7 ebx=00000004 ecx=00000000 edx=0023fe97 esi=00411749 edi=0023fee0 eip=0001747c esp=0023fe1c ebp=0023fef8 iopl=0 nv up ei pl nz na po nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202 0001747c? – EKI Nov 1 '10 at 14:56.

See, if you have some global instance(s) of class with constructor - if error is raised in constructor and class is declared globally (bad thing to do btw) - you'll get sigsegv even before main(). If you have such classes - try to refactor your code to have them inside main (or other function) - it will be easier to debug.

Try the following free MS tools - both are great for debugging this kind of problem. Application Verifier microsoft.com/downloads/en/details.aspx?... Gflags from Debugging Tools for Windows microsoft.com/downloads/en/details.aspx?....

Sounds to me like one of your DLL dependencies can't be loaded or instantiated correctly.

Also seriously consider actually fixing the warnings. Most of the time they are actual problems in the code that should be resolved. You should also try to see if this happens with a nearly empty main (comment out most/all of your code in main).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.