[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: Austin English <bugzilla_noreply () kde ! org>
Date: 2017-07-25 3:57:53
Message-ID: bug-382515-17878-np6CytxOmd () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #4 from Austin English <austinenglish@gmail.com> ---
(In reply to Philippe Waroquiers from comment #3)
> 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 ?
No, it does not. These files were produced by mingw64. File considers them
data:
/home/austin/.wine/drive_c/windows/mono/mono-2.0/lib/mono/4.5/mscorlib.pdb:
data
whereas real .pdb files from visual studio appear as:
./memory/mozalloc/mozalloc.pdb: MSVC program database ver
7.00, 4096*95 bytes
it's produced by Mingw, not Microsoft. Whereas my real pdb's first line is:
Microsoft C/C++ MSF 7.00
DS
The first hex character is 0x4D, however (maybe I'm misunderstanding what
you're asking).
FYI, I uploaded the file here:
http://austinenglish.com/files/for_valgrind/mscorlib.pdb
the genuine pdb files I used are at
https://phoenixnap.dl.sourceforge.net/project/wine/Wine%20Gecko/2.36/wine_gecko-2.36-x86-dbg-msvc-pdb.tar.bz2
> 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*
I'll get this in a bit or tomorrow.
--
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic