Bug 408758

Summary:	memcheck internal error: Signal 10 (SIGBUS)
Product:	[Developer tools] valgrind	Reporter:	John Ralls <jralls>
Component:	memcheck	Assignee:	Rhys Kidd <rhyskidd>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	pjfloyd, rhyskidd
Priority:	NOR
Version First Reported In:	3.14.0
Target Milestone:	---
Platform:	Other
OS:	macOS
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Session transcript of crashed memcheck session

Description John Ralls 2019-06-15 21:21:42 UTC

Created attachment 120903 [details]
Session transcript of crashed memcheck session

MacOS 10.11.6 with the 2019 security updates, Apple LLVM version 7.3.0 (clang-703.0.31), running in a VMWare Fusion 8.5.10 VM provisioned with 4 cores and 8GB of memory on a late 2013 MacPro running MacOS 10.14.
Valgrind was built from the 3.14.0 source tarball and configured with --with-64bitonly.

The program under test was Gramps (https://github.com/gramps-project/gramps) running in  a gtk-osx (https://gitlab.gnome.org/GNOME/gtk-osx) build environment with recent HEADS of glib (https://gitlab.gnome.org/GNOME/glib) and gtk-3-24 (https://gitlab.gnome.org/GNOME/gtk). Gramps is a Python program, and Python was version 3.6.8 built in the same environment. Python, glib, gtk, and most dependencies were built with -O0 -g. 

All of the session output is in the attachment.

Comment 1 John Ralls 2019-06-15 21:24:21 UTC

The command line for the crashed session was:
valgrind --log-file=gramps-memory --suppressions=$HOME/Development/gtk-sources/valgrind-3.15.0/darwin15.supp --suppressions=/Users/john/Development/Gramps-Build/gramps-stable-git-Mavericks/src/Python-3.6.8/Misc/valgrind-python.supp --main-stacksize=67108864 $PREFIX/bin/python $PREFIX/bin/gramps

The elevated --main-stacksize was necessary to avoid an earlier crash; in that case valgrind mentioned the stack size (8MB) and suggested increasing it.

Comment 2 Paul Floyd 2025-11-02 17:36:34 UTC

Closing this as I don't have access to a 10.11 machine.

Please reopen if you can reproduce the error on a 10.13 machine.