[valgrind] [Bug 393062] Reading build-id ELF note through phdrs triggers "debuginfo reader: ensure_valid failed"
https://bugs.kde.org/show_bug.cgi?id=393062 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Mark Wielaard --- The original issue was fixed by: commit f1f543a224eec5afd8cfddea70c1307ed0a20c55 Author: Mark Wielaard Date: Mon Apr 16 16:53:56 2018 +0200 Don't read build-id ELF Note in .debug file through phdrs. Bug #393062 - Reading build-id ELF note through phdrs triggers "debuginfo reader: ensure_valid failed" Skip the phdrs when we have to search the shdrs. In separate .debug files the phdrs might not be valid (they are a copy of the main ELF file) and might trigger assertions when getting image notes based on them. The report in comment #2 seems unrelated and there has been no follow-up on questions about platform. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393062] Reading build-id ELF note through phdrs triggers "debuginfo reader: ensure_valid failed"
https://bugs.kde.org/show_bug.cgi?id=393062 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #3 from Paul Floyd --- (In reply to willzhang...@foxmail.com from comment #2) > Created attachment 153823 [details] > Valgrind: during call to ML_(img_get_UChar) > > I met a problem when I use valgrind(3.19, 3.20) Which platform is this? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393062] Reading build-id ELF note through phdrs triggers "debuginfo reader: ensure_valid failed"
https://bugs.kde.org/show_bug.cgi?id=393062 willzhang...@foxmail.com changed: What|Removed |Added CC||willzhang...@foxmail.com Assignee|jsew...@acm.org |willzhang...@foxmail.com Resolution|FIXED |--- Status|RESOLVED|REPORTED --- Comment #2 from willzhang...@foxmail.com --- Created attachment 153823 --> https://bugs.kde.org/attachment.cgi?id=153823&action=edit Valgrind: during call to ML_(img_get_UChar) I met a problem when I use valgrind(3.19, 3.20) /oemdata/jmcotards # valgrind --tool=memcheck /mnt/ext_sdcard/valgrind/lib/ld-li nux.so.3 ./masterda ==20694== Memcheck, a memory error detector ==20694== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==20694== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info ==20694== Command: /mnt/ext_sdcard/valgrind/lib/ld-linux.so.3 ./masterda ==20694== ==20694== Valgrind: debuginfo reader: ensure_valid failed: ==20694== Valgrind: during call to ML_(img_get_UChar) ==20694== Valgrind: request for range [3555828, +1) exceeds ==20694== Valgrind: valid image size of 38868 for image: ==20694== Valgrind: "/mnt/ext_sdcard/valgrind/lib/ld-2.22.so" ==20694== ==20694== Valgrind: debuginfo reader: Possibly corrupted debuginfo file. ==20694== Valgrind: I can't recover. Giving up. Sorry. ==20694== -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393062] Reading build-id ELF note through phdrs triggers "debuginfo reader: ensure_valid failed"
https://bugs.kde.org/show_bug.cgi?id=393062 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Mark Wielaard --- commit f1f543a224eec5afd8cfddea70c1307ed0a20c55 Author: Mark Wielaard Date: Mon Apr 16 16:53:56 2018 +0200 Don't read build-id ELF Note in .debug file through phdrs. Bug #393062 - Reading build-id ELF note through phdrs triggers "debuginfo reader: ensure_valid failed" Skip the phdrs when we have to search the shdrs. In separate .debug files the phdrs might not be valid (they are a copy of the main ELF file) and might trigger assertions when getting image notes based on them. -- You are receiving this mail because: You are watching all bug changes.
