Ubuntu
upower package

upowerd crashed with SIGSEGV in __stpcpy_chk()

Bug #1206431 reported by sarwan kumar
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
New
Undecided
Unassigned

Bug Description

this issue occur after every 10 minute.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: upower 0.9.17-1build1
ProcVersionSignature: Ubuntu 3.5.0-37.58-generic 3.5.7.16
Uname: Linux 3.5.0-37-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Tue Jul 30 14:14:16 2013
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xb74c1b9e <__stpcpy_chk+30>: movzbl (%edx),%esi
 PC (0xb74c1b9e) ok
 source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
 __stpcpy_chk () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /usr/lib/libimobiledevice.so.3
 userpref_get_host_id () from /usr/lib/libimobiledevice.so.3
 lockdownd_client_new_with_handshake () from /usr/lib/libimobiledevice.so.3
 ?? ()
Title: upowerd crashed with SIGSEGV in __stpcpy_chk()
UpgradeStatus: Upgraded to quantal on 2013-07-30 (0 days ago)
UserGroups:

Revision history for this message
sarwan kumar (sarwan-kumar) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb74c1b9e in ___vfprintf_chk (fp=0x0, flag=-1074181788, format=0x840a460 "\020\344@\b\001", ap=0xb757a177 <mkdir_with_parents+55> "\300t6\350\221\346\377\377\203\070\021t,\211\064$\350t\346\377\377\211\004$\350\354\344\377\377\205\300\211\305t>\350\241\377\377\377\211,$\211\307\350\247\340\377\377\205\377t\033\215v") at vfprintf_chk.c:28
         done = <optimized out>
 #1 0xb758c000 in ?? () from /tmp/apport_sandbox_ReQRBD/usr/lib/libimobiledevice.so.3
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ___vfprintf_chk (fp=0x0, flag=-1074181788, format=0x840a460 "\020\344@\b\001", ap=0xb757a177 <mkdir_with_parents+55> "\300t6\350\221\346\377\377\203\070\021t,\211\064$\350t\346\377\377\211\004$\350\354\344\377\377\205\300\211\305t>\350\241\377\377\377\211,$\211\307\350\247\340\377\377\205\377t\033\215v") at vfprintf_chk.c:28
 ?? () from /tmp/apport_sandbox_ReQRBD/usr/lib/libimobiledevice.so.3

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Robert Ancell (robert-ancell)
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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