Need some "bad" code

[Magnum]

I have ollydbg set as my debugger.

There have been situations when a debugger should have opened, but neither Dr. Watson or Ollydbg opens up.

Does someone have some XP code that they know will open up the debugger.

Never thought I would be asking this.  :bg

[clive]

Usually such things throw up a "Please tell Microsoft about this problem." dialog in XP, with goto the debugger "Debug" as a option if Visual Studio, et al, are installed.

Writing something to NULL usually busts my applications, something like this should suffice.

XOR ECX,ECX
MOV [ECX],ECX

[Magnum]

Thanks clive.

Your code does bring up Ollydbg.

I am trying to track down the cause of this message in my Event Viewer and thought that it should have started Ollydbg.

Application Failure  explorer2.exe 6.0.2   900.2180   in shell32.dll
   6.0.2900.2180 at  offset 00023c3e 0d 0a       

I found this, and as a result I un-installed FaJo XP File Security Extension
to see if the error message stops appearing.

Typical this problem is caused by non Microsoft Explorer Shell Extensions and you can troubleshoot you can use AutoRuns for Windows to troubleshoot.  You can disable all of the Non-Microsoft shell extensions  and test to see if the problem occurs and then re-enable them 1 by 1 to see which one causes the problem.

[clive]

It brings up Visual Studio's debugger in my case. I normally just use Olly from the command line.