On 12-10-31 10:40 AM, Thomas Mashos wrote: > Shouldn't the crash file already be written to /var/crash/ ?
Interesting point. It doesn't seem to be the case however. Given this segfault: Oct 30 22:00:03 pvr kernel: [1937721.428406] mythbackend[13502]: segfault at 28 ip 0620ef91 sp b2ffe140 error 4 in libQtCore.so.4.8.1[607d000+2d4000] There was nothing in /var/crash about it. However given a different segfault: Oct 29 16:02:05 pvr kernel: [1829843.051149] mythcommflag[2020]: segfault at b37fb3f4 ip 080626cc sp bfa4d1f0 error 4 in mythcommflag[8048000+6e000] There is indeed a: -rw-r----- 1 mythtv mythtv 11878631 Oct 29 16:02 _usr_bin_mythcommflag.103.crash So what's different about these processes and why one's segfault is being caught by apport and the other is not? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073580 Title: mythtv-backend needs to run in writable directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1073580/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
