Hello!
Thanks for the backtrace you provided in your bug report!
It looks to me like the problem is in this snippet from libimobiledevice
src/lockdown.c :
/* set SystemBUID */
userpref_read_system_buid(&system_buid);
plist_dict_set_item(*pair_record, USERPREF_SYSTEM_BUID_KEY,
plist_new_string(system_buid));
userpref_read_system_buid, which calls usbmuxd_read_buid, fails for some reason
and system_buid remains/becomes NULL and when it gets passed as an argument
to plist_new_string being NULL the code explodes.
The return code from userpref_read_system_buid should be checked.
* @return 1 if the system buid could be retrieved or 0 otherwise.
Next question to investigate is why does usbmuxd_read_buid fail?
Do you think you could add a call to libusbmuxd_set_debug_level(99)
to libimobiledevice, build it and reproduce the problem and provide
the debug output from libusbmuxd? This should give us an idea
where it's failing.
(For reference see implementation of usbmuxd_read_buid:
http://anonscm.debian.org/gitweb/?p=pkg-gtkpod/packages/libusbmuxd.git;a=blob;f=src/libusbmuxd.c;h=6a6b3e686f95ddbdea2d11b5074f8016e24c795c;hb=HEAD#l1079
)
Regards,
Andreas Henriksson
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
