On Tue, Oct 11, 2011 at 03:00:27PM -0000, James Hunt wrote: > Hi Luke - my disassembly simply pointed to the source line that caused > the crash. However, we still don't know why the "source" object is NULL > (it should never be apparently). What we really need is a full core dump > to analyze
Given that this appears to be memory corruption, what we really need is enough information to *reproduce* the problem as a core dump is likely to only show that memory has been corrupted without giving us any hints to why. If someone is able to reproduce this at will and wants to try running plymouth under valgrind for us, that could be helpful. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/849414 Title: plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/849414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
