Nick Richards - 2008-11-24

I get a crash too - same function (test_bit) - when mounting my drive. The system pops up an anonymous error dialog claiming my drive is in need of repairs, however I think now this error belongs to the thing managing the e2fsck - and that if fsck dies the disk is blamed for the crash.

Intel MacBook Pro 10.5.5 USB mounted disk

= = = nearly identical crash dump = = =

Process: e2fsck [511]
Path: /usr/local/sbin/e2fsck
Identifier: e2fsck
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: fsck_ext2 [510]

Date/Time: 2008-11-23 19:20:16.975 -0800
OS Version: Mac OS X 10.5.5 (9F33)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000336a000
Crashed Thread: 0

Thread 0 Crashed:
0 e2fsck 0x000267bb ext2fs_set_bit + 32
1 e2fsck 0x000208b6 ext2fs_set_bitmap_padding + 55
2 e2fsck 0x000131be check_block_bitmaps + 1581
3 e2fsck 0x00012980 e2fsck_pass5 + 165
4 e2fsck 0x00005b08 e2fsck_run + 116
5 e2fsck 0x000051ba main + 2642
6 e2fsck 0x00001b7a _start + 228 (crt.c:272)
7 e2fsck 0x00001a95 start + 41

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x00012ba2 ecx: 0x00000000 edx: 0x03369ffd
edi: 0xbfffff14 esi: 0x049157c9 ebp: 0xbffffc18 esp: 0xbffffc00
ss: 0x0000001f efl: 0x00010246 eip: 0x000267bb cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x0336a000

Binary Images:
0x1000 - 0x39ff3 +e2fsck ??? (???) /usr/local/sbin/e2fsck
0x45000 - 0x49fff libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x1ee000 - 0x34eff3 libSystem.B.dylib ??? (???) <a12f397abf2285077b89bd726bff5b18> /usr/lib/libSystem.B.dylib
0x8fe00000 - 0x8fe2da53 dyld 96.2 (???) <7af47d3b00b2268947563c7fa8c59a07> /usr/lib/dyld
0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib