crash in LoggerClient.m with message " Crashed: Thread EXC_BAD_ACCESS KERN_INVALID_ADDRESS"

[nonstriater]

the crash report from Fabric as below:

Crashed: Thread
0  libobjc.A.dylib                0x3666faf6 objc_msgSend + 21
1  OneTravel                      0x368eb5 LoggerFlushQueueToBufferStream (LoggerClient.m:1355)
2  CoreFoundation                 0x24f647c7 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 14
3  CoreFoundation                 0x24f643b7 __CFRunLoopDoSources0 + 454
4  CoreFoundation                 0x24f6271f __CFRunLoopRun + 806
5  CoreFoundation                 0x24eb50d9 CFRunLoopRunSpecific + 516
6  CoreFoundation                 0x24eb4ecd CFRunLoopRunInMode + 108
7  OneTravel                      0x367903 LoggerWorkerThread (LoggerClient.m:597)
8  libsystem_pthread.dylib        0x36f1ec7f _pthread_body + 138
9  libsystem_pthread.dylib        0x36f1ebf3 _pthread_start + 110
10 libsystem_pthread.dylib        0x36f1ca08 thread_start + 8

LoggerClient.m:1355 line source code is "CFIndex dataLength = CFDataGetLength(data);" （not the newest version）。 the surrounded source codes are:

CFDataRef data = CFArrayGetValueAtIndex(logger->logQueue, 0);
CFIndex dataLength = CFDataGetLength(data);
CFIndex written = CFWriteStreamWrite(logger->bufferWriteStream, CFDataGetBytePtr(data), dataLength);

It seems that the 'data' is not CFDataRef type。

[fpillet]

Hrm wondering how this could happen... never seen this one before. How do you use NSLogger?