© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
Is this reproducible/has it ever happened again? As Scott says, the stack trace makes no sense, since kill() doesn't take pointer arguments.
Could it have been killed by some other process, or by the OOM-killer? (I'd expect that to use SIGKILL rather than SIGSEGV, though.)