Comment 6 for bug 837130
Revision history for this message
| PSWZ-ZhangY (pswzyu) wrote Re: [Bug 837130] Crash report cannot be processed | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hello!
Could you please tell me how to get the latest dbg packages? Which dbg
package do I need?
I have already updated my system before the apport caught the crash. And
till now there is no updates for my system.
Thanks a lot!
2011/8/30 Apport retracing service <email address hidden>
> Thank you for your report!
>
> However, processing it in order to get sufficient information for the
> developers failed (it does not generate an useful symbolic stack trace).
> This
> might be caused by some outdated packages which were installed on your
> system
> at the time of the report:
>
> libc6-i386 version 2.12.1-0ubuntu10.2 required, but 2.12.1-0ubuntu10.3 is
> available
> outdated debug symbol package for libkeyutils1: package version 1.4-1
> dbgsym version 1.2-12
> outdated debug symbol package for lib32stdc++6: package version
> 4.5.1-7ubuntu2 dbgsym version 4.4.3-4ubuntu5
> outdated debug symbol package for libidn11: package version 1.18-1 dbgsym
> version 1.15-2
> outdated debug symbol package for libattr1: package version 1:2.4.44-2
> dbgsym version 1:2.4.44-1
> libldap-2.4-2 version 2.4.23-0ubuntu3.5 required, but 2.4.23-0ubuntu3.6 is
> available
> outdated debug symbol package for libcups2: package version
> 1.4.4-6ubuntu2.3 dbgsym version 1.4.3-1ubuntu1.3
> libc-bin version 2.12.1-0ubuntu10.2 required, but 2.12.1-0ubuntu10.3 is
> available
> outdated debug symbol package for libdatrie1: package version 0.2.3-1
> dbgsym version 0.2.2-3
> outdated debug symbol package for libcurl3-gnutls: package version
> 7.21.0-1ubuntu1.1 dbgsym version 7.19.7-1ubuntu1
> outdated debug symbol package for coreutils: package version 8.5-1ubuntu3
> dbgsym version 7.4-2ubuntu3
> libc6 version 2.12.1-0ubuntu10.2 required, but 2.12.1-0ubuntu10.3 is
> available
> outdated debug symbol package for libthai0: package version 0.1.14-2 dbgsym
> version 0.1.13-1build1
>
>
> Please upgrade your system to the latest package versions. If you still
> encounter the crash, please file a new report.
>
> Thank you for your understanding, and sorry for the inconvenience!
>
>
> ** Attachment removed: "CoreDump.gz"
>
> https:/
>
> ** Tags removed: need-amd64-retrace
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> npviewer.bin crashed with SIGSEGV
>
> Status in “nspluginwrapper” package in Ubuntu:
> Invalid
>
> Bug description:
> I was viewing a webpage
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.10
> Package: nspluginwrapper 1.2.2-0ubuntu7
> ProcVersionSign
> Uname: Linux 2.6.35-30-generic x86_64
> NonfreeKernelMo
> Architecture: amd64
> CrashCounter: 1
> Date: Tue Aug 30 10:43:19 2011
> ExecutablePath: /usr/lib/
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> ProcCmdline: /usr/lib/
> /usr/lib/
> /org/wrapper/
> ProcEnviron:
> LANGUAGE=zh_CN:zh
> LANG=zh_CN.utf8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0xf5ffa2d6: movl $0x0,0x218(%eax)
> PC (0xf5ffa2d6) ok
> source "$0x0" ok
> destination "0x218(%eax)" (0x00000218) not located in a known VMA region
> (needed writable region)!
> SegvReason: writing NULL VMA
> Signal: 11
> SourcePackage: nspluginwrapper
> StacktraceTop:
> ?? () from /usr/lib/
> ?? () from /usr/lib/
> ?? () from /usr/lib/
> ?? () from /usr/lib/
> ?? () from /usr/lib/
> Title: npviewer.bin crashed with SIGSEGV
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
>
> To manage notifications about this bug go to:
>
> https:/
>