[Mono-devel-list] mono debugger in infinite loop

[Martin Baulig]

Hi Philip,

Philip Nelson <panmanphil at yahoo.com> writes:

> Also, the dialog handling to load a new program needs a little work.  If you
> click the Browse button, the new dialog is locked, unless you kill the initial
> dialog.  Then you can choose a file and say OK, but nothing happens. Open the
> choose dialog again, the file selected is there and can be loaded.

I can reproduce this, thanks for the bug report, I'll fix it asap.

> Also I hadn't noticed the step over vs step command, but the results were the
> same.  It would make sense perhaps if I tried to step into a method for which
> there were no symbols, but alas, that wasn't the problem.

"Step Into (F8)" never steps into a method which has no symbols "Instruction Step Into
(F6)" does this.

> Filename: /home/panmanphil/nant/src/NAnt.Console/ConsoleStub.cs
> 
> Unhandled Exception: System.NullReferenceException: A null value was found
> where an object instance was required
> in <0x00020> 00 Gtk.TextBuffer:MoveMark (Gtk.TextMark,Gtk.TextIter)
> in <0x00290> 00 Mono.Debugger.GUI.SourceView:frame_changed_event
> (Mono.Debugger.StackFrame)

Hmm, this looks like a bug which I fixed about a week ago, but not sure.

> It crashes in various places.  Today I made it through to the return statement
> with the step over (F9).  Second pass it locked on the line: 
> 
> System.Data.DataSet test = new System.Data.DataSet("test");
> 
> Third time, after killing some zombie debugger and mono processes, on the call
> to Console.WriteLn()

Ok, I'll have a look at this.

-- 
Martin Baulig
martin at gnome.org
martin at ximian.com