[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 382515] valgrind: "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/
From:       Philippe Waroquiers <bugzilla_noreply () kde ! org>
Date:       2017-07-22 9:41:18
Message-ID: bug-382515-17878-XQvVzlw2C4 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #3 from Philippe Waroquiers <philippe.waroquiers@skynet.be> ---
The dll and pdb being loaded are:
mscorlib.dll
mscorlib.pdb

Looking at the trace compared to the code, once we have seen the traces

==22926== LOAD_PDB_DEBUGINFO:   Scanning PE section .reloc at avma 0x7ac000
svma 0x3ac000
--22926-- LOAD_PDB_DEBUGINFO: rx_map: avma 0x402000 size 3831716 foff 512
--22926-- LOAD_PDB_DEBUGINFO: rw_map: avma 0x7aa000 size    1024 foff 3832320
--22926-- LOAD_PDB_DEBUGINFO:   text: avma 0x402000 svma 0x2000 size 3831716
bias 0x0

there is only one place where the readpdb code returns without dinfo, that is:
   hdr = find_pdb_header( pdbimage, &signature );
   if (0==hdr)
      return False; /* JRS: significance? no pdb header? */

This find_pdb_header is searching for a specific character '\032'
and the string "Microsoft C/C++"
Is the pdb file containing the expected pdb header ?
I guess wine and/or microsoft-windows have objdump like utilities ?
Or else just look with emacs this pdb and another working pdb, to
see if the expected data is there ?

Would be good also to redo the tracing above adding something like
--trace-symtab=yes --trace-symtab-patt=*mscorlib*

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]