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

--- Comment #30 from Austin English <austinengl...@gmail.com> ---
Created attachment 128946
  --> https://bugs.kde.org/attachment.cgi?id=128946&action=edit
compiled test/pdb

(In reply to Jefferson Carpenter from comment #29)
> (In reply to Austin English from comment #28)
> > Created attachment 128170 [details]
> > the impossible happened
> > 
> > Upon manual review, it didn't assert, but the impossible happened:
> >                                     
> > PUTI(136:8xI8)[t1,0] = 0x0:I8                                               
> > 
> >                                                                             
> > 
> > vex: the `impossible' happened:                                             
> > 
> >    stmt_is_guardable: unhandled stmt                                        
> > 
> > vex storage: T total 9579053828 bytes allocated                             
> > 
> > vex storage: P total 496 bytes allocated                                    
> > 
> >                                                                             
> > 
> > valgrind: the 'impossible' happened:                                        
> > 
> >    LibVEX called failure_exit().                                            
> > 
> >                                      
> > 
> > in dlls/atl/tests/registrar.c
> 
> I ran the same test (valgrind --trace-children=yes
> ../../../../wine-source/tools/runtest -q -P ../../../loader/wine -T ../../..
> -M atl.dll -p atl_test.exe.so registrar), and the impossible didn't happen
> on my machine.  (My configure command included --without-mingw because
> that's what causes the .exe.so files to be generated).  Can you confirm that
> the bug happens with my patch applied and not on master?  It seems like some
> spooky action at a distance if my patch caused new problems generating IR.

After some more testing, it only occurs if:
./configure --with-mingw CROSSDEBUG=pdb

is used for the build.

I'm not sure why the other log shows .exe.so. Maybe a dirty tree, or maybe
wine's build system changed.. I've attached the exe and pdb file, it should be
enough to reproduce without having to get llvm-mingw/rebuild wine.

$ export VALGRIND_OPTS="-q --trace-children=yes --track-origins=yes
--gen-suppressions=all
--suppressions=/home/austin/wine-valgrind/tools/valgrind/valgrind-suppressions-ignore
--suppressions=/home/austin/wine-valgrind/tools/valgrind/valgrind-suppressions-external
--suppressions=/home/austin/wine-valgrind/tools/valgrind/valgrind-suppressions-known-bugs
--suppressions=/home/austin/wine-valgrind/tools/valgrind/valgrind-suppressions-gecko
--leak-check=full --num-callers=20 --workaround-gcc296-bugs=yes
--vex-iropt-register-updates=allregs-at-mem-access"

# make sure to use the full path for wine:
$ valgrind /usr/local/bin/wine avifil32_test.exe api

preloader: Warning: failed to reserve range 00110000-68000000
preloader: Warning: failed to reserve range 7f000000-82000000
0140:err:heap:HEAP_GetPtr Invalid heap (nil)!
size: 136926
==31466== LOAD_PDB_DEBUGINFO: Find PDB file: /tmp/valgrind_petmp31466_1cb84028
is empty
==31466== Warning: Missing or un-stat-able
/home/austin/.wine/drive_c/windows/system32/kernelbase.pdb
size: 135558
==31466== LOAD_PDB_DEBUGINFO: Find PDB file: /tmp/valgrind_petmp31466_1cb84028
is empty
==31466== Warning: Missing or un-stat-able /usr/local/lib64/wine/kernelbase.pdb
symbol table size is 0.  Not reading debug information for
/tmp/tmp.emEgO3p387/bug-211031-avifil32-test/avifil32_test.exe

valgrind: m_debuginfo/debuginfo.c:1672 (vgPlain_di_notify_pdb_debuginfo):
Assertion 'di && !di->fsm.have_rx_map && !di->fsm.have_rw_map' failed.

host stacktrace:
==31466==    at 0x58041CF9: show_sched_status_wrk (m_libcassert.c:406)
==31466==    by 0x58041E20: report_and_quit (m_libcassert.c:477)
==31466==    by 0x58041F14: vgPlain_assert_fail (m_libcassert.c:543)
==31466==    by 0x58076146: vgPlain_di_notify_pdb_debuginfo (debuginfo.c:1672)
==31466==    by 0x580A252D: do_client_request (scheduler.c:2121)
==31466==    by 0x580A252D: vgPlain_scheduler (scheduler.c:1516)
==31466==    by 0x580F72C2: thread_wrapper (syswrap-linux.c:101)
==31466==    by 0x580F72C2: run_a_thread_NORETURN (syswrap-linux.c:154)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 31466)
==31466==    at 0x7BCD6494: map_image (virtual.c:1749)
==31466==    by 0x7BCD6A71: virtual_map_section (virtual.c:1835)
==31466==    by 0x7BC79293: open_dll_file (loader.c:2371)
==31466==    by 0x7BC79D9E: find_dll_file (loader.c:3014)
==31466==    by 0x7BC7FDAB: load_dll (loader.c:3044)
==31466==    by 0x7BC84857: __wine_process_init (loader.c:4426)
==31466==    by 0x7BC84F42: __wine_set_unix_funcs (loader.c:4488)
==31466==    by 0x7C001341: main (main.c:285)
client stack range: [0xFECB8000 0xFECBDFFF] client SP: 0xFECBA900
valgrind stack range: [0x881FD000 0x882FCFFF] top usage: 7372 of 1048576

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

Reply via email to