Bug 491450

Summary:	Memcheck: mc_main.c:5874 (vgMemCheck_is_valid_aligned_word): Assertion 'VG_IS_WORD_ALIGNED(a)' failed.
Product:	[Developer tools] valgrind	Reporter:	Tarek Saad <tsaad>
Component:	memcheck	Assignee:	Julian Seward <jseward>
Status:	RESOLVED WAITINGFORINFO
Severity:	normal	CC:	pjfloyd
Priority:	NOR
Version First Reported In:	3.19.0
Target Milestone:	---
Platform:	Other
OS:	Other
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Tarek Saad 2024-08-08 19:38:15 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
I hit the assertion error while running valgrind on my process. Is there a workaround to suppress this? 

==9065== HEAP SUMMARY:
==9065==     in use at exit: 40,377,245 bytes in 7,630 blocks
==9065==   total heap usage: 67,218 allocs, 59,198 frees, 82,763,859 bytes allocated
==9065==

Memcheck: mc_main.c:5874 (vgMemCheck_is_valid_aligned_word): Assertion 'VG_IS_WORD_ALIGNED(a)' failed.

host stacktrace:
==9065==    at 0x5804A35C: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==9065==    by 0x5804A487: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==9065==    by 0x5804A62D: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==9065==    by 0x58013641: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==9065==    by 0x58000948: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==9065==    by 0x5800167F: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==9065==    by 0x58001B22: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==9065==    by 0x58003A9E: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==9065==    by 0x580072A2: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==9065==    by 0x580C4333: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)
==9065==    by 0x580FAE37: ??? (in /usr/libexec/valgrind/memcheck-amd64-linux)

sched status:
  running_tid=1


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Paul Floyd 2024-08-09 04:42:38 UTC

Can you reproduce this with a small example?

Which version of Valgrind are you using.

We can’t help much without more information.