There are actually a lot of "normal" exceptions thrown during startup of any windows program.  You should set your debugger, if possible, to catch just the unhandled ones.  Or, turn off exception catching altogether, and reenable it when you reach a breakpoint just before where the actual trouble begins.

Hope that helps -


On Thu, Apr 24, 2014 at 3:07 AM, Witold E Wolski <> wrote:
I am trying to debug the following exception :

Files\ProteoWizard\ProteoWizard\qtofpeakpicker.exe" --in "c:\test\HEK
2ug IDA CoV17.0 SV3750 1.wiff" --out y:/Analysis/xxx.mzML

Unhandled Exception: System.AccessViolationException: Attempted to
read or write protected memory. This is often an indication that other
memory is corrupt.
   at mainCRTStartup()

c:\Program Files\ProteoWizard\ProteoWizard
points to a pwiz installation downloaded from the pwiz site.

I can't debug this exception.  When I am running my debug build I
never get this far.
A different exception is thrown right at the start.

--in "c:\test\HEK 2ug IDA CoV17.0 SV3750 1.wiff" --out

Unhandled Exception: System.Runtime.InteropServices.SEHException:
External component has thrown an exception.
   at _mainCRTStartup()

I am wondering if I am missing some additional build step?


Witold Eryk Wolski

Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
proteowizard-developer mailing list