maze crashed with SIGSEGV in __libc_start_main()

Bug #1063802 reported by W. Scott Lockwood III on 2012-10-08
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xscreensaver (Ubuntu)
Undecided
Unassigned

Bug Description

Machine was idle over the weekend, crash was not observed personally.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xscreensaver-data-extra 5.15-2ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.16-lowlatency 3.5.5
Uname: Linux 3.5.0-17-lowlatency x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Fri Oct 5 17:14:56 2012
ExecutablePath: /usr/lib/xscreensaver/maze
InstallationMedia: Ubuntu-Studio 12.04 "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: maze -root
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x404639: movzwl 0x4(%rbx,%rdx,2),%edx
 PC (0x00404639) ok
 source "0x4(%rbx,%rdx,2)" (0x7f0d442748c8) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xscreensaver
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
Title: maze crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to quantal on 2012-09-10 (27 days ago)
UserGroups: adm administrators audio cdrom dip lpadmin plugdev sambashare sudo users

W. Scott Lockwood III (wsl3) wrote :

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1056858, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers