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

Bug #750688 reported by Eric Gregory on 2011-04-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libgpod (Ubuntu)

Bug Description

Happened when I plugged in my iPhone and attempted to unmount the two mount that appeared. Why TWO mounts appeared for ONE device is a little odd as well.)

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libgpod-common 0.7.95-1build2
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CrashCounter: 1
Date: Mon Apr 4 12:53:42 2011
ExecutablePath: /lib/udev/iphone-set-info
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
ProcCmdline: /lib/udev/iphone-set-info

 Segfault happened at: 0x1a3706 <__strlen_sse2_bsf+22>: movdqu (%edi),%xmm1
 PC (0x001a3706) ok
 source "(%edi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libgpod
 __strlen_sse2_bsf () at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:52
 plist_get_string_val () from /usr/lib/libplist.so.1
 ?? ()
 ?? ()
 __libc_start_main (main=0x8048c60, argc=1, ubp_av=0xbfd77c14, init=0x80492d0, fini=0x8049330, rtld_fini=0x59ea50, stack_end=0xbfd77c0c) at libc-start.c:226
Title: iphone-set-info crashed with SIGSEGV in __strlen_sse2_bsf()
UpgradeStatus: No upgrade log present (probably fresh install)

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #730356, 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-i386-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers