emacs24-x crashed with SIGSEGV in __mpn_mul()

Bug #1062616 reported by Anders Kaseorg
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
emacs24 (Ubuntu)
New
Medium
Unassigned

Bug Description

This happened during an apt upgrade.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: emacs24 24.1+1-2ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Oct 5 17:50:10 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/emacs24-x
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
ProcCmdline: emacs --daemon
Signal: 11
SourcePackage: emacs24
StacktraceTop: __mpn_mul (prodp=<optimized out>, prodp@entry=<error reading variable: Cannot access memory at address 0x8>, up=<error reading variable: Cannot access memory at address 0xffffffffffffffc8>, up@entry=<error reading variable: Cannot access memory at address 0x8>, usize=1024, usize@entry=<error reading variable: Cannot access memory at address 0x8>, vp=<optimized out>, vp@entry=<error reading variable: Cannot access memory at address 0x8>, vsize=<optimized out>, vsize@entry=<error reading variable: Cannot access memory at address 0x8>) at mul.c:108
Title: emacs24-x crashed with SIGSEGV in __mpn_mul()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare sudo wireshark

Revision history for this message
Anders Kaseorg (andersk) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007fa6f10eb6e7 in __mpn_mul (prodp=<optimized out>, prodp@entry=<error reading variable: Cannot access memory at address 0x8>, up=<error reading variable: Cannot access memory at address 0xffffffffffffffc8>, up@entry=<error reading variable: Cannot access memory at address 0x8>, usize=1024, usize@entry=<error reading variable: Cannot access memory at address 0x8>, vp=<optimized out>, vp@entry=<error reading variable: Cannot access memory at address 0x8>, vsize=<optimized out>, vsize@entry=<error reading variable: Cannot access memory at address 0x8>) at mul.c:108
   [Error: mul.c was not found in source tree]
StacktraceTop: __mpn_mul (prodp=<optimized out>, prodp@entry=<error reading variable: Cannot access memory at address 0x8>, up=<error reading variable: Cannot access memory at address 0xffffffffffffffc8>, up@entry=<error reading variable: Cannot access memory at address 0x8>, usize=1024, usize@entry=<error reading variable: Cannot access memory at address 0x8>, vp=<optimized out>, vp@entry=<error reading variable: Cannot access memory at address 0x8>, vsize=<optimized out>, vsize@entry=<error reading variable: Cannot access memory at address 0x8>) at mul.c:108

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in emacs24 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Anders Kaseorg (andersk)
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.