CODEWITHSUNDEEP
iosxcode
Samoka
Samoka

Reputation: 1333

only (lldb) output in debug area, no other message

I got a rare problem that randomly when I ran my app in xcode, the simulator will stop and in the debug area only "(lldb)" is shown. It is random because when I ran again without modifying my code, it will run. What could have been the problem? I tried it in my other projects but still the same. Thank you.

xcode 4.6.2 Mountain Lion 10.8.4 (lldb error starts after updating 10.8.4 from 10.8.3, I don't know if this has some impact on xcode)

update1 - result from Douglas

(lldb) bt
* thread #1: tid = 0x1c03, 0x94f06a6a libsystem_kernel.dylib`__pthread_kill + 10, stop reason = signal SIGABRT
frame #0: 0x94f06a6a libsystem_kernel.dylib`__pthread_kill + 10
frame #1: 0x907b1b2f libsystem_c.dylib`pthread_kill + 101
frame #2: 0x018db57b libsystem_sim_c.dylib`abort + 140
frame #3: 0x01f45b4e GraphicsServices`GSRegisterPurpleNamedPort + 348
frame #4: 0x01f4569f GraphicsServices`_GSEventInitialize + 123
frame #5: 0x01f45c1f GraphicsServices`GSEventInitialize + 36
frame #6: 0x0027ed99 UIKit`UIApplicationMain + 600
frame #7: 0x00001ccd sampleapp`main(argc=1, argv=0xbffff3a0) + 141 at main.m:16

Upvotes: 16

Views: 11746

Answers (4)

Flimm
Flimm

Reputation: 151268

When I ran into a similar issue, it was because I somehow accidentally set a breakpoint on a line of code. Just click on the blue ribbon on the line of code to unset it.

Upvotes: 0

Steve
Steve

Reputation: 756

I had the same output with only "(lldb)" being displayed. I could re-create the app crashing, though I couldn't really see why the certain steps should cause the app to crash? However, (from my initial tests) I am unable to crash the app running on an actual phone, which suggests to me something is dodgy with the simulator.

Xcode 7/7.2.1 iPhone 5S running iOS 9.2.1

Upvotes: 0

CampbellGolf
CampbellGolf

Reputation: 822

I just posted the same question and seemed to have fixed my own issue:

SIGABRT Error - Exactly after 3rd Run (both iPhone & iPad Simulators)

This appears to have resolved my issue:

Update your scheme by selecting Product > Scheme > Edit Scheme, and choose the GDB debugger for your debug scheme from the Info Tab.

The default was: LLDB

Be aware of the 2 debuggers: GDB Vs LLDB debuggers

Upvotes: 1

Douglas
Douglas

Reputation: 2524

In the debug area, after you see the lldb, type in bt, this will show you the crash log. Hopefully this will give you some insight as to what caused the crash/stop.

Upvotes: 20

Related Questions