If a program has crashed in malloc then it's already too late to debug.
Unfortunately heap corruption has a delayed effect so even a perfect
backtrace of such a crash won't tell you exactly where the corruption
originated. You would need to use tooling such as Valgrind to debug the
source of the corruption.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Changed in: glibc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647710
Title:
gnome-shell crashed with SIGSEGV in _int_malloc()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1647710/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
