https://bugs.kde.org/show_bug.cgi?id=382515
Austin English changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #13 from Philippe Waroquiers ---
Thanks for the testing
Patch committed as revision 16465.
As discussed in comment 12, really handling this kind of debug info
will be another bug (if needed)
--
You are
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #12 from Austin English ---
(In reply to Philippe Waroquiers from comment #11)
> Note that the patch is compiling on linux, but is completely untested.
> So, expect fire, smoke and explosions ...
Thanks Philippe,
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #11 from Philippe Waroquiers ---
Note that the patch is compiling on linux, but is completely untested.
So, expect fire, smoke and explosions ...
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #10 from Philippe Waroquiers ---
Created attachment 106973
--> https://bugs.kde.org/attachment.cgi?id=106973=edit
better report/handle and survive to invalid/unexpected pdb format
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #9 from Philippe Waroquiers ---
Can you try the attached patch ? This produces more user messages when it
cannot
read a pdb file.
Also, it should recover properly from an invalid/unsupported pdb file.
Note
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #8 from Austin English ---
(In reply to Philippe Waroquiers from comment #6)
> The valgrind code expects something very precise as a header.
> See function static void* find_pdb_header( void* pdbimage,
>
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #7 from Austin English ---
Created attachment 106926
--> https://bugs.kde.org/attachment.cgi?id=106926=edit
debug log 2
with --trace-symtab=yes --trace-symtab-patt=*mscorlib*
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #6 from Philippe Waroquiers ---
mscorelib.pdb starts with:
0005342424a00010001000c
B S J B 001 \0 001 \0 \0 \0 \0 \0 \f \0 \0 \0
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #5 from Austin English ---
Forgot to say, first line of mingw64's pdb is:
BSJB PDB V1.0
first character is \042
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #4 from Austin English ---
(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
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #3 from Philippe Waroquiers ---
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
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #2 from Austin English ---
Created attachment 106785
--> https://bugs.kde.org/attachment.cgi?id=106785=edit
debug log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382515
Philippe Waroquiers changed:
What|Removed |Added
CC|
14 matches
Mail list logo