vsjitdebugger error?

I have a native win32 c++ application which I'd like to debug. It's a
service, so I'm using Image File Execution Options / Debugger /
vsjitdebugger.exe to debug the startup routine. Problem is, when I
try to start it I get

An error occured while launching 'myservice.exe':
%1 is not a valid Win32 application.
Check the documentation index for 'Just-in-time debugging, errors' for
more information.

Obviously I did RTFM but nothing was mentioned about this error. Of
course, it actually is a valid Win32 application. I can run it from
the command line just fine (assuming I remove the Debugger value from
IFEO in the registry).

Any reason why this might be happening?

Advice appreciated
.

Relevant Pages

  • Re: How to connect to children process
    ... Main problem is amount of manual operations required per debug cycle. ... connection to DLL with debugger takes sensible amount of time and manual ... Is the main problem that the debugger keeps symbols file loaded ... AFAIK that's how VS2003 debugger works, but WinDbg should usually ...
    (microsoft.public.vsnet.debugging)
  • Re: Need Help Debugging
    ... you should use straight and plain ADPlus.VBS from the debugger package. ... debug info loaded, etc... ... does that avoid using the stack ?!? ... which is our custom CRITICAL_SECTION class. ...
    (microsoft.public.win32.programmer.kernel)
  • gnome-settings-daemon crashed twice
    ... To debug your program, run it with the --sync command line ... backtrace from your debugger if you break on the gdk_x_errorfunction.) ...
    (GNOME)
  • Re: DesignBAIS/Dave Bryant
    ... As Tony says you can also "debug" your code in the DB app (browser ... form of tcl access and are able to enter the native debugger anyway. ... i could enter the debugger on their public internet site they would ... Not all Visage applications are deployed to Public internet sites. ...
    (comp.databases.pick)
  • Re: SUnit disappointment
    ... I always press the 'Debug' button in the SUnitBrowser when I'm ... For example when examining a failure in the debugger rather ... I'll often be able to fix the failure in my second ... > Equals verify: object printString with: 'test' ...
    (comp.lang.smalltalk.dolphin)