[Bug 29614] WinRAR viewer crashes on a particular file

[wine-bugs at winehq.org]

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

--- Comment #22 from Artem S. Tashkinov <t.artem at mailcity.com> ---
(In reply to Austin English from comment #21)
> (In reply to comment #20)
> > (In reply to comment #19)
> > > Can you try with march please?
> > 
> > What -march? ;-)
> 
> Without*

Unhandled exception: assertion failed in 32-bit code (0xb77d4cac).
Register dump:
 CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
 EIP:b77d4cac ESP:003258b4 EBP:003258cc EFLAGS:00000202(   - --  I   - - - )
 EAX:00000000 EBX:00003aa4 ECX:00003aa4 EDX:00000006
 ESI:00000000 EDI:b75b6ff4
Stack dump:
0x003258b4:  003258cc 00000006 00003aa4 b744e861
0x003258c4:  b75b6ff4 003259ec 003259f4 b745013a
0x003258d4:  00000006 0032596c 00000000 7d9e7690
0x003258e4:  b75b83d0 b75b6ff4 b75b83a0 00000000
0x003258f4:  00325914 00000001 b75b83a0 00000078
0x00325904:  7d9e7690 b75b6ff4 0000006e 0000006d
Backtrace:
=>0 0xb77d4cac __kernel_vsyscall+0x10() in [vdso].so (0x003258cc)
  1 0xb744e861 gsignal+0x50() in libc.so.6 (0x003258cc)
  2 0xb745013a abort+0x179() in libc.so.6 (0x003259f4)
  3 0xb7447b7b __assert_fail_base+0x14a() in libc.so.6 (0x00325a38)
  4 0xb7447c36 __assert_fail+0x55() in libc.so.6 (0x00325a58)
  5 0x7ac1765a ME_MoveCaret+0x369() in riched20 (0x00325ae8)
  6 0x7ac2a651 ME_PaintContent+0xc0() in riched20 (0x00325b78)
  7 0x7ac26475 RichEditWndProc_common+0x3b4() in riched20 (0x00325c38)
  8 0x7ac267ef RichEditWndProcW+0x2e() in riched20 (0x00325c68)
  9 0x7eb1f06a WINPROC_wrapper+0x19() in user32 (0x00325c98)
  10 0x7eb1f7ec call_window_proc+0x5b() in user32 (0x00325ce8)
  11 0x7eb21cd0 WINPROC_call_window+0x10f() in user32 (0x00325d38)
  12 0x7eae1962 DispatchMessageW+0xb1() in user32 (0x00325e48)
  13 0x004c1612 in winrar (+0xc1611) (0x7eaac830)
  14 0xfff0e483 (0x04244c8d)
0xb77d4cac __kernel_vsyscall+0x10 in [vdso].so: popl    %ebp

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.