Hi, On Sat, Jul 28, 2012 at 3:50 AM, dermotos <[email protected]> wrote:
> Does anyone else experience random lockups/freezes of their app when > debugging? > > It may indeed be some deadlocks in my code, but before I go hunting for > them > I thought id check incase maybe its a debugger issue. > Strange thing is it only seems to happen when debugging, but I know from > experience that issues like deadlocks/race conditions etc can often happen > when the debugger is attached, simply because it may slow down certain > parts > of the code, and cause the issue to manifest itself (rather than being an > actual problem with the debugger). > There have been several bugs with the debugger that causes lockups / freezes, but it could also be your own code. The easiest way to determine this is to get a native stack trace for all threads for the app: Find the pid of the app - it is printed to the application output in MonoDevelop at startup. Then execute from a terminal: > gdb program <PID> (gdb will attach, some output until a gdb prompt appears:) $(gdb) thread apply all backtrace (gdb will print stack traces for all threads). Get all the output from the terminal, save it to a file and send it to the lists, and we'll easily be able to figure out if it's a deadlock in your code or if it's in the debugger. Rolf > > > > -- > View this message in context: > http://monotouch.2284126.n4.nabble.com/lockups-during-debugging-or-deadlocks-in-my-code-tp4656215.html > Sent from the MonoTouch mailing list archive at Nabble.com. > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch >
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
