Xcode: lockdown_connection_destroy

After a reboot I opened DiskUtility, and clicked verify disk on the main system disk.
Xcode started (automatically because it was open before the shut-down) and crashed with the following report:

Process:         Xcode [178]
Path:            /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier:      com.apple.dt.Xcode
Version:         4.6.2 (2067.2)
Build Info:      IDEApplication-2067002000000000~2
App Item ID:     497799835
App External ID: 15055625
Code Type:       X86-64 (Native)

Date/Time:       2013-05-14 18:07:50.136 +0200

OS Version:      Mac OS X 10.8.3 (12D78)

Crashed Thread:  7  Dispatch queue: gputools.DYMobileDevice.0x40260e0a0.main

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000010000000108

VM Regions Near 0x10000000108:

    MALLOC (reserved)      0000000608000000-0000000800000000 [  7.9G] rw-/rwx SM=NUL  reserved VM address space (unallocated)

--> 

    JS JIT generated code  00005f925b400000-00005f925b401000 [    4K] ---/rwx SM=NUL  

Application Specific Information:

ProductBuildVersion: 4H1003

objc[178]: garbage collection is ON

Thread 7 Crashed:: Dispatch queue: gputools.DYMobileDevice.0x40260e0a0.main

0   com.apple.mobiledevice         0x00000001112a0b24 lockdown_connection_destroy + 14

1   com.apple.mobiledevice         0x00000001112a3a87 AMDeviceDisconnect + 44

2   com.apple.mobiledevice         0x00000001112a3900 AMDeviceConnect + 103

3   com.apple.GPUToolsMobileFoundation 0x0000000113030dae -[DYMobileDevice _startSession:] + 54

4   com.apple.GPUToolsMobileFoundation 0x000000011303108f -[DYMobileDevice _runInSession:] + 41

5   com.apple.GPUToolsMobileFoundation 0x0000000113031229 -[DYMobileDevice _cacheCommonAttributes:] + 162

6   com.apple.GPUToolsMobileFoundation 0x0000000113030a02 __39-[DYMobileDevice setAppleMobileDevice:]_block_invoke_2 + 165

7   libdispatch.dylib             0x00007fff947f50b6 _dispatch_client_callout + 8

8   libdispatch.dylib             0x00007fff947f6723 _dispatch_barrier_sync_f_invoke + 39

9   com.apple.GPUToolsMobileFoundation 0x0000000113030903 __39-[DYMobileDevice setAppleMobileDevice:]_block_invoke + 127

10  libdispatch.dylib             0x00007fff947f50b6 _dispatch_client_callout + 8

11  libdispatch.dylib             0x00007fff947f6723 _dispatch_barrier_sync_f_invoke + 39

12  com.apple.GPUToolsMobileFoundation 0x000000011303087b -[DYMobileDevice setAppleMobileDevice:] + 97

13  com.apple.GPUToolsMobileFoundation 0x000000011303626b __47-[DYMobileDeviceManager _handleDeviceAttached:]_block_invoke + 224

14  libdispatch.dylib             0x00007fff947f8f01 _dispatch_call_block_and_release + 15

15  libdispatch.dylib             0x00007fff947f50b6 _dispatch_client_callout + 8

16  libdispatch.dylib             0x00007fff947f647f _dispatch_queue_drain + 235

17  libdispatch.dylib             0x00007fff947f62f1 _dispatch_queue_invoke + 52

18  libdispatch.dylib             0x00007fff947f61c3 _dispatch_worker_thread2 + 249

19  libsystem_c.dylib             0x00007fff8e276d0b _pthread_wqthread + 404

20  libsystem_c.dylib             0x00007fff8e2611d1 start_wqthread + 13

It seems that the GPU might not have been in the stat that Xcode expected.