[Mono-dev] (no subject)
krapfenbauer at ICT.TUWIEN.AC.AT
Mon Jun 4 03:45:15 EDT 2007
I recently investigated the mono debugger and it looks quite good and
stable for mono c# development. however, I have some questions...
1) changing variables
the mono web site states that the debugger is able to "Inspect and
change static and instance fields, local variables, and parameters
[DONE]." inspecting variables etc. does work, but I did not found a
command to change them. what's the current status or what is the correct
2) ironpython support
debugging mono assemblies that were created by ironpython (i used 1.1)
is partly working. I can set line breakpoints, next-stepping works, and
source code lines of python code are also shown. (I saved the .exe
before with -X:SaveAssemblies.) what's annoying is that the debugger
always steps into the ironpython source code. furthermore, inspecting
python variables does not work.
say, I want to enhance mdb with ironpython support, what would I need to
implement? create a new namespace Mono.Debugger.Languages.IronPython?
3) remote debugging support
Say, I want to have remote debugging with mdb where mdb shall run on the
host and the debugee runs on the target.
I investigated mdb's source code and came to the following approach: For
the host, the libmonodebuggerserver library does not issue the ptrace()
commands locally, but send the commands via TCP/IP to the target. On the
target, a small server listens, takes the commands, and executes the
ptrace() commands locally. this would be similar to gdb and gdbserver.
what do you think about this approach? would it be feasible and a good
solution? are there any traps you think of?
More information about the Mono-devel-list