[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 rber...@codeweavers.com changed: What|Removed |Added Attachment #133748|0 |1 is obsolete|

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #35 from rber...@codeweavers.com --- Talked too soon, it now doesn't build anymore, I'll update the patches. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #34 from rber...@codeweavers.com --- Just a reminder that this is still broken and the patches attached should fix the missing symbols when Wine is built with MinGW and DWARF debug info (still requires some Wine-side fixes too). I believe

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #33 from Austin English --- To follow up, I misunderstood the scope of Remi's work. The patchset *does* work for DWARF symbols in PE binaries in modern wine (i.e., with wine having a mingw compiled ntdll). PDB support is a separate

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #32 from Austin English --- Hi Remi, Using both wine patches: https://source.winehq.org/patches/data/196764 https://source.winehq.org/patches/data/196765 and valgrind patches: https://sourceforge.net/p/valgrind/mailman/message/37164939/

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 rber...@codeweavers.com changed: What|Removed |Added CC||rber...@codeweavers.com --- Comment

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #30 from Austin English --- Created attachment 128946 --> https://bugs.kde.org/attachment.cgi?id=128946=edit compiled test/pdb (In reply to Jefferson Carpenter from comment #29) > (In reply to Austin English from comment #28) > > Created

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #29 from Jefferson Carpenter --- (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: >

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #28 from Austin English --- Created attachment 128170 --> https://bugs.kde.org/attachment.cgi?id=128170=edit the impossible happened Upon manual review, it didn't assert, but the impossible happened: PUTI(136:8xI8)[t1,0] = 0x0:I8

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #27 from Austin English --- No assertions so far (running still, up to d3d8:visual). Stacktraces look good. Lots of (valid) warnings for missing symbols in wine: symbol table size is 0. Not reading debug information for

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 Jefferson Carpenter changed: What|Removed |Added Attachment #126950|0 |1 is obsolete|

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #25 from Jefferson Carpenter --- Removed the spurious output. Did not manually add a mapping, to fix the "DiCfsi invariant (1) verification failed" message. Also removed the dwarf3 code - the patch still seems to work for me, and native

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #24 from Austin English --- Getting a failed assertion in some tests: valgrind: m_debuginfo/debuginfo.c:694 (check_CFSI_related_invariants): Assertion '!ranges_overlap(map->avma, map->size, map2->avma, map2->size)' failed. valgrind: DiCfsi

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #23 from Austin English --- I usually use -p1, so not sure what was wrong..anyway, recently tried again, with a clean tree, and it applies fine, so yeah, it was something on my end. With the patch, I see an improvement using badfree.c from

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 Timur Iskhodzhanov changed: What|Removed |Added CC|timur...@google.com | -- You are receiving this mail because:

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 Timur Iskhodzhanov changed: What|Removed |Added CC||timur...@google.com -- You are receiving

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #22 from Jefferson Carpenter --- (In reply to Jefferson Carpenter from comment #21) > I created the patch using git format-patch, so you should apply it using > either > > $ git apply 0001-Add-read_pe_debug_info-V2.patch > > or > > $

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #21 from Jefferson Carpenter --- (In reply to Austin English from comment #20) > Fails to build: > make[3]: *** No rule to make target 'm_debuginfo/readpe.c', needed by > 'm_debuginfo/libcoregrind_amd64_linux_a-readpe.o'. Stop. > > (try 1

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #20 from Austin English --- (In reply to Jefferson Carpenter from comment #19) > Created attachment 126977 [details] > Hackish patch: Add read_pe_debug_info: v2 > > Fixed some of the most significant lies from my first patch. No longer >

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #19 from Jefferson Carpenter --- Created attachment 126977 --> https://bugs.kde.org/attachment.cgi?id=126977=edit Hackish patch: Add read_pe_debug_info: v2 Fixed some of the most significant lies from my first patch. No longer assumes

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #18 from Jefferson Carpenter --- Created attachment 126950 --> https://bugs.kde.org/attachment.cgi?id=126950=edit Hackish patch: Add read_pe_debug_info -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 Jefferson Carpenter changed: What|Removed |Added CC||jeffersoncarpenter2@gmail.c

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #16 from Austin English --- I recently tested llvm-mingw (from https://github.com/mstorsjo/llvm-mingw/), and built wine with llvm's pdb debug symbols. That gives similar results to gnu mingw: ==23786== Invalid read of size 2 ==23786==at

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #15 from Austin English --- As of wine-4.6, wine now supports building its dlls with mingw: https://source.winehq.org/git/wine.git/commitdiff/a3cf86a18446e9d7df4e045b83d3aa3d9193512a the plan is to eventually make that the default (not

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #14 from Austin English --- (In reply to Austin English from comment #13) > This is also relevant again for wine-gecko. Upstream Firefox moved to > require Visual Studio 2013+, and those newer format PDBs don't work

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

https://bugs.kde.org/show_bug.cgi?id=211031 cpon changed: What|Removed |Added CC||cpigat...@gmail.com -- You are