Segmentation fault
While trying to activate my (yes, I know its better to use itunes) iPod touch (4.1 ipt2.5g), I keep getting:
Creating activation request Segmentation fault
on 4.1 and 4.0. and any other firmware. Whats up? And I tried all the flags.
What arch? And this was never tested with beta firmwares...
I'm seeing this as well on iPhone 3G, iOS 4.0.2
Core was generated by `./ideviceactivate'. Program terminated with signal 11, Segmentation fault. #0 0x0000000000401cfa in activate_fetch_record (client=0xee4100, record=0x7fff38a1e3a8, cust_imei=0x0, cust_imsi=0x0, cust_iccid=0x0, cust_serial_num=0x0) at activate.c:86 86 ainfo->iccid=(char*)lockdownd_get_string_value(client, "IntegratedCircuitCardIdentity");
This is on F13 x86_64
32 bit. and its not just with betas.
Can you try the new version in my fork?
With the latest from boxing squirrel:
Starting program: /home/rryder/git/ideviceactivate-boxingsquirrel/ideviceactivate/src/ideviceactivate -d [Thread debugging using libthread_db enabled] Creating activation request
Program received signal SIGSEGV, Segmentation fault.
0x0000003975a02548 in plist_get_type_and_value (node=
After grabbing the latest plist and rebuilding libimobildevice and both versions of ideviceactivate it shows this:
Creating activation request
Entity: line 8: parser error : PCDATA invalid Char value 1
Backtrace from gdb:
Thread 1 (Thread 0xb7fe0730 (LWP 11618)):
#0 0x00cd91c0 in xmlFreeNodeList () from /usr/lib/libxml2.so.2
#1 0x00cd9309 in xmlFreeNodeList () from /usr/lib/libxml2.so.2
#2 0x00cd9309 in xmlFreeNodeList () from /usr/lib/libxml2.so.2
#3 0x00cd9309 in xmlFreeNodeList () from /usr/lib/libxml2.so.2
#4 0x00cd9063 in xmlFreeDoc () from /usr/lib/libxml2.so.2
#5 0x00cd44bb in xmlSAXParseMemoryWithData () from /usr/lib/libxml2.so.2
#6 0x00cd44ff in xmlSAXParseMemory () from /usr/lib/libxml2.so.2
#7 0x00cd4569 in xmlParseMemory () from /usr/lib/libxml2.so.2
#8 0x00131742 in plist_from_xml () from /usr/local/lib/libplist.so.1
#9 0x00117eb9 in internal_plist_receive_timeout (
client=
The last letter of "International" in the string is represented by a unicode symbol (box with 0 0 0 1 in it)
hmmm...try @p0sixninja's original commit. I'm trying to figure out if it always had this problem or if it's something I did...