alarmclock crashed with SIGSEGV in update_list_entries()

Bug #528452 reported by DebianSidUser
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
alarm-clock (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: alarm-clock

alarmclock crashed with SIGSEGV in update_list_entries()

ProblemType: Crash
Architecture: amd64
Date: Fri Feb 26 07:23:31 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/alarmclock
NonfreeKernelModules: nvidia
Package: alarm-clock 1.2.5-1
ProcCmdline: alarmclock
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0x409dea <update_list_entries+1338>: mov 0x0(%rbp),%rdi
 PC (0x00409dea) ok
 source "0x0(%rbp)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: alarm-clock
StacktraceTop:
 update_list_entries ()
 alarm_thread ()
 ?? () from /lib/libglib-2.0.so.0
 start_thread () from /lib/libpthread.so.0
 clone () from /lib/libc.so.6
Title: alarmclock crashed with SIGSEGV in update_list_entries()
Uname: Linux 2.6.32-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
DebianSidUser (raza) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 update_list_entries () at main_list.c:308
 alarm_thread () at alarm_thread.c:549
 ?? () from /lib/libglib-2.0.so.0
 start_thread () from /lib/libpthread.so.0
 clone ()

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 alarm-clock (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in alarm-clock (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version has expired long time ago, and is no more supported

Changed in alarm-clock (Ubuntu):
status: Confirmed → Invalid
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.