GDB: data formatters temporarily unavailable, will retry after continue

[TheFabolusBensun]

I'm getting the error...

GDB: Data Formatters temporarily unavailable, will re-try after a 'continue'. (Unknown error loading shared library "/Developer/usr/lib/libXcodeDebuggerSupport.dylib")

The console says....

Program received signal: “EXC_BAD_ACCESS”.
Data Formatters temporarily unavailable, will re-try after a 'continue'. (Unknown error loading shared library "/Developer/usr/lib/libXcodeDebuggerSupport.dylib")
kill
quit

The Debugger has exited with status 0.(gdb)



I have no Idea what this means and nether does google. Has anyone seen this before?

[iahmed]

Originally Posted by TheFabolusBensun

I'm getting the error...

GDB: Data Formatters temporarily unavailable, will re-try after a 'continue'. (Unknown error loading shared library "/Developer/usr/lib/libXcodeDebuggerSupport.dylib")

The console says....

Program received signal: “EXC_BAD_ACCESS”.
Data Formatters temporarily unavailable, will re-try after a 'continue'. (Unknown error loading shared library "/Developer/usr/lib/libXcodeDebuggerSupport.dylib")
kill
quit

The Debugger has exited with status 0.(gdb)



I have no Idea what this means and nether does google. Has anyone seen this before?

I have the same issue. Did you ever find a solution?

I know mine has something to do with allocating objects and then adding those objects in an array.

[surgen12]

I got a same problem.
and ihamed's experience gave me a hint.
And I found the problem.

In my case, I did below
sqlite3_reset(statement);
sqlite3_finalize(statement);
and I did it again!
with out making it fresh.

so I put this code in the if(){} phrase.

now it's okay.

[regmee]

I could run my project on Simulator-3.2 | Debug , The same message popped up when I tried to run on Simulator-3.1.3 | Debug. I simply reverted back to the 3.2 setting and it worked like a charm.

Hope this could help at least a few.

[mkp]

I've had the "Data Formatters temporarily unavailable..." problem when I put a breakpoint in an unusual position (such as on the exception handler). In the Debugger window, click on "Show Breakpoints" and see if you have something you forgot about -- I did.