In #8, wrote: > I've had this occur a few times recently; I am using the default byobu > profile, on a 64-bit system with 4 GiB of RAM. > > Each time the crash has occurred, I'm exiting vim when signed in from SSH, > and the vim/screen session was started from the local desktop. > > The following line appears in dmesg: > > [919845.653676] screen[22768]: segfault at 18 ip 00007f55568ab120 sp > 00007ffff3f35b30 error 4 in libc-2.12.1.so[7f5556831000+17a000]
I've also had this when exiting vim, but not from SSH; I had reattached to an existing screen session. And I get a similar segfault message, although I'm on 32-bit: [67596.757458] screen[3297]: segfault at c ip 003d38b8 sp bfa0263c error 4 in libc-2.12.1.so[366000+157000] I'm curious as to why apport doesn't pick up this segfault and write a core dump. Any ideas? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/644825 Title: screen unpredictably crashes -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
