Could you repeat your test with MALLOC_CHECK_=2 set in the environment
(yes, the trailing underscore is deliberate)? Unfortunately the stack
trace you provided indicates that the damage was done before the program
actually managed to crash, and so we can't tell what happened;
MALLOC_CHECK_=2 ought to encourage it to crash earlier so that we can
see the actual problem.
** Changed in: parted (Ubuntu)
Assignee: (unassigned) => Colin Watson (kamion)
Status: New => Incomplete
--
parted crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/203000
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
