iphone-set-info crashed with SIGSEGV in __stpcpy_chk()

Bug #1039320 reported by Chanchao
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libgpod (Ubuntu)
New
Undecided
Unassigned

Bug Description

This is a re-occurrence of #1035263 ; in there not enough information was supplied, so was asked to submit a new bug report if it occurred again. It just occurred again, just after booting up. No external display involved this time, and no devices of any kind connected. (So no iPhone connected)

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: libgpod-common 0.8.2-6build1
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
CrashCounter: 1
Date: Mon Aug 20 13:02:51 2012
ExecutablePath: /lib/udev/iphone-set-info
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: /lib/udev/iphone-set-info
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f03c26a2b50 <__stpcpy_chk+80>: mov (%rsi),%rax
 PC (0x7f03c26a2b50) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libgpod
StacktraceTop:
 __stpcpy_chk () from /lib/x86_64-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
 _start ()
Title: iphone-set-info crashed with SIGSEGV in __stpcpy_chk()
UpgradeStatus: Upgraded to quantal on 2012-07-28 (23 days ago)
UserGroups:

Revision history for this message
Chanchao (custom) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1034067, 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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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