14.04.2013 Views

The Path to Better Debugging on iOS

The Path to Better Debugging on iOS

The Path to Better Debugging on iOS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<str<strong>on</strong>g>The</str<strong>on</strong>g>re’s more than just po, you know?<br />

Command Abbrev. Descripti<strong>on</strong><br />

c<strong>on</strong>tinue c C<strong>on</strong>tinue until the next breakpoint<br />

step [count] s Single step the next [count] statements. Step in<str<strong>on</strong>g>to</str<strong>on</strong>g> functi<strong>on</strong>s.<br />

next [count] n Single step the next [count] statements. Step over functi<strong>on</strong>s.<br />

finish p Execute the rest of the current functi<strong>on</strong>. Step out of the functi<strong>on</strong>.<br />

print expressi<strong>on</strong> p Print the value of an expressi<strong>on</strong><br />

print-object obj po Print the value of [obj debugDescripti<strong>on</strong>].<br />

set var = exp - Set a variable. e.g. set obj = (void *)[[NSObject alloc] init]<br />

call expressi<strong>on</strong> c Call a functi<strong>on</strong>. e.g. call NSLog(@”Can’t break the habit.”)<br />

jump line j C<strong>on</strong>tinue at a given line (or address).<br />

backtrace [count] bt Print a backtrace of [count] frames.<br />

return [expressi<strong>on</strong>] - Return the value of [expressi<strong>on</strong>] <str<strong>on</strong>g>to</str<strong>on</strong>g> the previous stack frame.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!