https://bugs.kde.org/show_bug.cgi?id=487744
Bug ID: 487744
Summary: [PATCH] Valgrind coredumps greater than 4GB are
unusable and GDB does not interpret them
Classification: Developer tools
Product: valgrind
Version: 3.23.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: chandru....@gmail.com
Target Milestone: ---
Created attachment 169938
--> https://bugs.kde.org/attachment.cgi?id=169938&action=edit
Patch to fix offset overflow
SUMMARY
When Valgrind coredumps exceed 4GB, an overflow occurs while computing
the offset, leading to the corruption of previously written valid
sections.
STEPS TO REPRODUCE
1. Run a large binary whose coredump is expected to exceed 4GB in valgrind.
eg: /usr/bin/valgrind --tool=memcheck --track-fds=yes --run-libc-freeres=no
--log-file=/valgrind.log --fair-sched=yes --num-callers=20 --leak-check=full
--error-limit=no --show-reachable=yes /usr/bin/large_binary
2. Trigger a coredump by sending a kill signal to the valgrind (kill -11 <pid>)
3. Try and examine the resulting coredump generated, using GDB.
OBSERVED RESULT
GDB is not able to load the shared libraries and the backtrace is not shown
properly
EXPECTED RESULT
The coredump under GDB should give clear stack traces.
SOFTWARE/OS VERSIONS
Linux
--
You are receiving this mail because:
You are watching all bug changes.
