https://bugs.kde.org/show_bug.cgi?id=380869

Henri Verbeet <hverb...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hverb...@gmail.com

--- Comment #1 from Henri Verbeet <hverb...@gmail.com> ---
Actually, those are probably distinct issues, and it's not clear to me (yet)
whether the latter is a Valgrind issue.

(In reply to Austin English from comment #0)
> While running wine's direct3d tests (which invoke OpenGL), I noticed that I
> got a lot of crashes, with poor debugging info:
> Backtrace:
> =>0 0x063bcd77 in swrast_dri.so (+0x59d77) (0x1535f9c0)
>   1 0x063bd6d9 in swrast_dri.so (+0x5a6d8) (0x00000000)
>   2 0x063c11de in swrast_dri.so (+0x5e1dd) (0x00000000)
>   3 0x0659825e in swrast_dri.so (+0x23525d) (0x1535f7f0)
>   4 0x066dadf3 in swrast_dri.so (+0x377df2) (0x1535f7f0)
>   5 0x066d9abf in swrast_dri.so (+0x376abe) (0x1535f3a8)
>   6 0x05cf1959 in libgl.so.1 (+0x3e958) (0x1535f3a8)
>   7 0x05cca866 glXMakeContextCurrent+0x95() in libgl.so.1 (0x0460c3c0)
>   8 0x05ccaa86 glXMakeCurrent+0x15() in libgl.so.1 (0x04b8f2d8)
>   9 0x05935782 X11DRV_WineGL_InitOpenglInfo+0x2fe()
> [/home/austin/wine-valgrind/dlls/winex11.drv/opengl.c:502] in winex11
> (0x04b8f2d8)
>   10 0x05936f92 init_opengl+0xfbe(once=0x5993e00, param=0x0(nil),
> context=(nil)) [/home/austin/wine-valgrind/dlls/winex11.drv/opengl.c:679] in
> winex11 (0x04b8f4e8)
> 
> 
Important context in the original output is the following:

    wine: Unhandled illegal instruction at address 0x63bcd77 (thread 0150),
starting debugger...
    Unhandled exception: illegal instruction in 32-bit code (0x063bcd77).
    ...
    Backtrace:
    ...
    0x063bcd77: repe

I.e., it looks to me like the issue is the repe/repz. Unfortunately I can't
tell from that output what instruction repe is supposed to apply to. I imagine
a dump of the affected code would be potentially useful, unless this bug report
is a duplicate of a known issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to