zsh4 crashed with SIGSEGV in init_jobs()

Bug #565321 reported by Jan Hülsbergen
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
zsh (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: zsh

A few minutes after my reboot for the -21 kernel and before actively launching any terminals, apport threw this in my face. (I was actually just playing around with lernid at the time)

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: zsh 4.3.10-5ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Sat Apr 17 13:22:28 2010
ExecutablePath: /bin/zsh4
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline:

ProcEnviron:
 LANG=en_US.utf8
 PATH=(custom, user)
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7fc4414dc1e6: movdqa (%rdi),%xmm0
 PC (0x7fc4414dc1e6) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: zsh
StacktraceTop:
 ?? () from /lib/libc.so.6
 init_jobs ()
 zsh_main ()
 __libc_start_main () from /lib/libc.so.6
 _start ()
Title: zsh4 crashed with SIGSEGV in init_jobs()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jan Hülsbergen (jan-afoo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __rawmemchr_sse2 () at ../sysdeps/x86_64/multiarch/../rawmemchr.S:31
 init_jobs ()
 zsh_main ()
 __libc_start_main (main=<value optimized out>,
 _start ()

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 zsh (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Daniel Hahler (blueyed)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in zsh (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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