Summary: | Reading build-id ELF note through phdrs triggers "debuginfo reader: ensure_valid failed" | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Mark Wielaard <mark> |
Component: | general | Assignee: | willzhang121 <willzhang121> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | pjfloyd, willzhang121 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
URL: | https://bugzilla.redhat.com/show_bug.cgi?id=1566639 | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Valgrind: during call to ML_(img_get_UChar) |
Description
Mark Wielaard
2018-04-12 19:49:32 UTC
commit f1f543a224eec5afd8cfddea70c1307ed0a20c55 Author: Mark Wielaard <mark@klomp.org> 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. Created attachment 153823 [details]
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==
(In reply to willzhang121@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? The original issue was fixed by: commit f1f543a224eec5afd8cfddea70c1307ed0a20c55 Author: Mark Wielaard <mark@klomp.org> 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. |