https://bugs.kde.org/show_bug.cgi?id=480405
Bug ID: 480405
Summary: valgrind 3.22.0 "m_debuginfo/image.c:586 (set_CEnt):
Assertion '!sr_isError(sr)' failed."
Classification: Developer tools
Product: valgrind
Version: 3.22.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: bugs...@bromberger.com
Target Milestone: ---
SUMMARY
***
Valgrind seems to throw an error when checking my code. Error is as follows:
***
STEPS TO REPRODUCE
1. Download and build https://github.com/sbromberger/finddups-cpp
2. run `valgrind --leak-check=yes ./finddups`
OBSERVED RESULT
https://dpaste.org/OTor0:
```
seth@hydrogen:~/dev/cpp/finddups î‚ master $ valgrind --leak-check=yes ./finddups
.
==6333== Memcheck, a memory error detector
==6333== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==6333== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==6333== Command: ./finddups .
==6333==
min size: 0, max size: 9223372036854775807, includes: [], excludes: []
sizemap size = 181
finished sizemap
valgrind: m_debuginfo/image.c:586 (set_CEnt): Assertion '!sr_isError(sr)'
failed.
host stacktrace:
==6333== at 0x58065812: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==6333== by 0x58065867: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==6333== by 0x5806887B: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==6333== by 0x580C4DA5: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==6333== by 0x5813A08A: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==6333== by 0x5813E232: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==6333== by 0x58144CAC: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==6333== by 0x581B4456: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==6333== by 0x581B5CB8: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable syscall 9 (lwpid 6333)
==6333== at 0x4D0F0A2: __mmap64 (mmap64.c:58)
==6333== by 0x4D0F0A2: mmap (mmap64.c:46)
==6333== by 0x11292A: hashmap(std::unordered_map<unsigned long,
std::vector<std::filesystem::__cxx11::directory_entry, std
::allocator<std::filesystem::__cxx11::directory_entry> >, std::hash<unsigned
long>, std::equal_to<unsigned long>, std::alloca
tor<std::pair<unsigned long const,
std::vector<std::filesystem::__cxx11::directory_entry,
std::allocator<std::filesystem::__c
xx11::directory_entry> > > > > const&, Config const&) (in
/home/seth/dev/cpp/finddups/finddups)
==6333== by 0x110073: main (in /home/seth/dev/cpp/finddups/finddups)
client stack range: [0x1FFEFFE000 0x1FFF000FFF] client SP: 0x1FFEFFFA58
valgrind stack range: [0x1002CB2000 0x1002DB1FFF] top usage: 13144 of 1048576
<Note and other boilerplate text elided>
```
EXPECTED RESULT
Something else (unknown as this is my first time running valgrind).
SOFTWARE/OS VERSIONS
Linux: Void Linux `Void 6.6.11_1 x86_64 AuthenticAMD uptodate rFFF`
ADDITIONAL INFORMATION
valgrind on system utilities (`df` and `ls` tested) seems to work fine.
--
You are receiving this mail because:
You are watching all bug changes.
