[Bug 28316] New: kernel32/debugger.ok: exit status of debugger is sometimes 0 when it should be STATUS_ACCESS_VIOLATION

http://bugs.winehq.org/show_bug.cgi?id=28316

Summary: kernel32/debugger.ok: exit status of debugger is
                    sometimes 0 when it should be STATUS_ACCESS_VIOLATION
           Product: Wine
           Version: 1.1.3
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P2
         Component: kernel32
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Back in
http://www.winehq.org/pipermail/wine-devel/2008-September/069299.html
I reported that test
kernel32:debugger.c:300: Test failed: exit code = 00000000
failed in 2 out of 1000 runs.

It is still showing up with roughly that frequency today; I just
saw it after three or so days.
( http://buildbot.kegel.com/builders/runtests-heaptest/builds/43 )
Here's the current log (the backtrace is expected, it's the exit status 
that is in question):

../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p
kernel32_test.exe.so debugger.c && touch debugger.ok
...
Backtrace:
=>0 doCrash+0x92(argc=0x3, argv=0x112d98)
[build/dlls/kernel32/tests/debugger.c:177]
  1 func_debugger+0x12d() [build/dlls/kernel32/tests/debugger.c:677]
  2 run_test+0x9e(name="debugger")
[build/dlls/kernel32/tests/../../../include/wine/test.h:556]
  ...
doCrash+0x92 [dlls/kernel32/tests/debugger.c:177] : movb    $0x0,0x0(%eax)
177        *p=0;
...
err:seh:setup_exception_record nested exception on signal stack in thread 0015
eip 7bc7b228 esp 7ffdbc7c stack 0x252000-0x350000
debugger.c:410: Test failed: exit code = 00000000
(when it wanted STATUS_ACCESS_VIOLATION).

In an adjacent good run, that 
"extra err:seh:setup_exception_record nested exception..."
line is not present.

This run was with WINEDEBUG=warn-heap, but I doubt that matters.