[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.

[Bug 28316] 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

--- Comment #1 from Dan Kegel  2011-09-12 08:59:53 CDT ---
It happened again, so I'm blacklisting kernel32/tests/debugger.ok for the 
moment on the buildbot.

Again, I saw
err:seh:setup_exception_record nested exception on signal stack in thread 001b
eip 7bc7b218 esp 7ffdbc7c stack 0x252000-0x350000
right before the error.

Also, it was on a system with WINEDEBUG=warn+heap again, maybe that matters
after all.

System info:
os:     Ubuntu 10.04.3 LTS, 2.6.32-33-generic, pulseaudio
0.9.21-63-gd3efa-dirty, Advanced Linux Sound Architecture Driver Version
1.0.21.
ram:    3212 MB
cpu:    Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
gpu:    GeForce GT 240/PCI/SSE2 3.2.0 NVIDIA 195.36.24

[Bug 28316] 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

--- Comment #2 from Dan Kegel  2011-09-23 08:48:58 CDT ---
Happened again, this time without WINEDEBUG=warn+heap,
Same system,

os:     Ubuntu 10.04.3 LTS, 2.6.32-33-generic, pulseaudio
0.9.21-63-gd3efa-dirty, Advanced Linux Sound Architecture Driver Version
1.0.21.
ram:    3212 MB
cpu:    Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
gpu:    GeForce GT 240/PCI/SSE2 3.2.0 NVIDIA 195.36.24

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

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

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Anastasius Focht  ---
Hello Dan,

is this still a problem?
If not please resolve.

Maybe you can also check your hundreds of other open bugs and update the status
(preferably before the universe dies the heat death).

Regards

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

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

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Austin English  ---
(In reply to Anastasius Focht from comment #3)
> Hello Dan,
>
> is this still a problem?
> If not please resolve.
>
> Maybe you can also check your hundreds of other open bugs and update the
> status (preferably before the universe dies the heat death).
>
> Regards

I just ran it in a loop, 1000 times with warn+heap, 1000 times without, both
passed.

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

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

--- Comment #5 from Austin English  ---
Using wine-1.7.16-199-ga6e53ea

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

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

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #6 from Alexandre Julliard  ---
Closing bugs fixed in 1.7.17.