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

[Loïc Minier]

Hi,

Getting crahes in libimobiledevice4 when plugging an iPad under latest saucy; seems to be in udev rules, but also gettting nautilus error popups.

Also reproduced with ifuse; under gdb:
(gdb) bt
#0 0x00007ffff798c872 in property_list_service_client_new ()
   from /usr/lib/libimobiledevice.so.4
#1 0x00007ffff7995511 in house_arrest_client_new ()
   from /usr/lib/libimobiledevice.so.4
#2 0x0000000000401912 in ?? ()
#3 0x00007ffff71b6de5 in __libc_start_main (main=0x4016f0, argc=4,
    ubp_av=0x7fffffffe3f8, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffffffe3e8) at libc-start.c:260
#4 0x0000000000401c18 in ?? ()

Cheers,

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: libgpod-common 0.8.2-7ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Sun Sep 1 22:11:23 2013
ExecutablePath: /lib/udev/iphone-set-info
MarkForUpload: True
ProcCmdline: /lib/udev/iphone-set-info
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f4d8022dce6 <lockdownd_start_service+54>: movb $0x0,0x2(%rax)
 PC (0x7f4d8022dce6) ok
 source "$0x0" ok
 destination "0x2(%rax)" (0xd270000000000002) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: libgpod
Stacktrace:
 #0 0x00007f4d8022dce6 in lockdownd_start_service () from /usr/lib/libimobiledevice.so.4
 No symbol table info available.
 #1 0x0000000000401690 in _start ()
 No symbol table info available.
StacktraceTop:
 lockdownd_start_service () from /usr/lib/libimobiledevice.so.4
 _start ()
Title: iphone-set-info crashed with SIGSEGV in lockdownd_start_service()
UpgradeStatus: Upgraded to saucy on 2013-01-09 (235 days ago)
UserGroups:

[Loïc Minier (lool)]

NB: please keep this bug private as I suspect it might contain private information such as device ids.

[Apport retracing service (apport)]

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 #1212546, 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.

[Loïc Minier (lool)]

w/ debug symbols:
(gdb) bt
#0 0x00007ffff798c872 in property_list_service_client_new (device=0x606110,
    service=0xcb10, client=0xffffff00) at property_list_service.c:71
#1 0x00007ffff7995511 in house_arrest_client_new (device=<optimized out>,
    service=<optimized out>, client=0x6054d8) at house_arrest.c:72
#2 0x0000000000401912 in ?? ()
#3 0x00007ffff71b6de5 in __libc_start_main (main=0x4016f0, argc=4,
    ubp_av=0x7fffffffe3f8, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffffffe3e8) at libc-start.c:260
#4 0x0000000000401c18 in ?? ()

Looks like memory corruption:
(gdb) print *service
Cannot access memory at address 0xcb10

Lots of mem leak fixes in what seems to be an upstream git repo:
http://cgit.sukimashita.com/libimobiledevice.git/log/