Thanks Curt, I should referenced the following link: http://forums.msdn.microsoft.com/en-US/netfxtoolsdev/thread/34b32f85-13cf-4613- 86a5-3d2464661530/
Mike Stall mentions that there may be a MDbg parser problem with dynamic languages and hints that there might be an updated release of MDbg that fixes this. I was just following up on this... Thanks, Mitch Quoting Curt Hagenlocher <[EMAIL PROTECTED]>: > We're not going to do anything specific to support MDbg (or vice versa, as > far as I know) -- but we shouldn't have to. IronPython emits the same kind > of line number metadata that C# emits, so any managed debugger ought to be > able to follow right along. > > On Wed, Aug 6, 2008 at 9:16 AM, <[EMAIL PROTECTED]> wrote: > > > Congratulations on the release of IP2B4! > > > > I have a quick question with respect to IP2 and MDbg - will MDbg be > updated > > to > > work with the DLR? I know there are a few issues using a debugger with > > dynamic > > languages, but not insurmountable as MDbg is a great base to work from > > (thanks > > to Mike Stall!) > > > > My point is that for folks that are implementing tooling around the DLR > > (e.g. > > consoles, IDE's, and possibly new dynamic languages), having a debugger > > would > > seem to be desirable... > > > > http://softwareindustrialization.com/WebbasedDLRIDEWithMDbgDebugger.aspx > > > > > > Thanks, > > > > Mitch > > _______________________________________________ > > Users mailing list > > [email protected] > > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > > > _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
