[Bug 188537] Re: nautilus crashed with SIGSEGV
The bug might be fixed with the new versions, closing this one if you run into the issue again could you open a new one using apport so it's retraced? ** Changed in: nautilus (Ubuntu) Status: Incomplete = Invalid -- nautilus crashed with SIGSEGV https://bugs.launchpad.net/bugs/188537 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 188537] Re: nautilus crashed with SIGSEGV
Will do. Thanks! -- nautilus crashed with SIGSEGV https://bugs.launchpad.net/bugs/188537 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 188537] Re: nautilus crashed with SIGSEGV
Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. ** Changed in: nautilus (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) Status: New = Incomplete ** Attachment removed: CoreDump.gz http://launchpadlibrarian.net/11740025/CoreDump.gz ** Visibility changed to: Public -- nautilus crashed with SIGSEGV https://bugs.launchpad.net/bugs/188537 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 188537] Re: nautilus crashed with SIGSEGV
Pedro, thanks for your pointers. I'm a nubie but was able to figure out that I needed to install nautilus-dbgsym to get a backtrace. If I run gdb nautilus and set a breakpoint at main I can get a backtrace with symbols, however if I unzip CoreDump.gz and run gdb nautilus ~/Desktop/CoreDump I get the following error: Cannot access memory at address 0xb7fac658. Backtrace produces a similar error: #0 0xb75ee837 in ?? () Cannot access memory at address 0xbfdfbb64 Unfortunately when I installed nautilus-dbgsym I think it also upgraded nautilus, so the symbols probably no longer match CoreDump at the time of the crash, and I haven't seen this crash repeat. Are we SOL or is there some way to recover a backtrace at this point? If you could give me a pointer to forcing load of old symbols or some other technique I will be happy to try again after work tomorrow (machine is at home). -- nautilus crashed with SIGSEGV https://bugs.launchpad.net/bugs/188537 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
