[MonoDevelop] Remote debugging support?

[Michael Hutchinson]

On Tue, Aug 2, 2011 at 6:22 AM, Ian Norton
<ian.norton-badrul at thales-esecurity.com> wrote:
> On Fri, Jun 10, 2011 at 10:10:00AM +0100, Michael Hutchinson wrote:
>> On Tue, May 31, 2011 at 9:05 PM, Martin Pilot <mpilot at matrox.com> wrote:
>> > Sorry if this is known info, but I’ve been spending way too much time now
>> > looking for this to no avail…
>> >
>> > Is there a way to perform remote debugging with MonoDevelop? Just to be
>> > clear, by this I mean executing in debug mode an EXE on a remote system.
>> >
>> > By digging in the MonoDevelop.Debugger.Soft sources, I found a way to enable
>> > CustomSoftDebuggerEngine, which has a proto UI allowing me to specify the IP
>> > address of the target machine by defining MONODEVELOP_SDB_TEST as an
>> > environment variable. All my efforts to get this to work failed miserably,
>> > with the debugger being stuck showing “Waiting for debugger to connect”.
>> >
>> > Any info on this? What server should run on the debuggee side? Another
>> > instance of MonoDevelop? Monotools-server?
>>
>> Start Mono on the target with the commandline arguments
>> --debug --debugger-agent=transport=dt_socket,address=${IP}:{${Port}
>> and the debugger agent inside the runtime will connect out to the IDE
>> listening on IP:port.
>>
>> The CustomSoftDebuggerSession GUI has a field for launching a process
>> that you could use to kick this off over ssh, and it can automatically
>> substitute the variables AgentArgs, IP, Port, Console, e.g.
>> --debugger-agent=${AgentArgs}
>
> Hi Mike,
>
> I've been trying to get the same things working and havn't had any luck at all.
> Neither with server=y or not on the debugee.
>
> I've even tried running this on a single host and using 127.0.0.1 addresses, MD
> simply stays saying 'waiting for debugger'
>
> This is what I'm trying:
>
> IP: 127.0.0.1
> Port: 10000
> [Listen]
>
> mono --debug \
> --debugger-agent=transport=dt_socket,address=127.0.0.1:10000 \
> remotehello.exe
>
> I thought I'd have more luck if I ran the debuggee as a server but can't get
> far with that either, not sure what 'output port' means in the MD dialog.
>
> Hope you can help.

Sorry for the late reply, I haven't been paying enough attention to
the mailing list recently.

Server means that the app starts a server and waits for MD to connect to it.

Output port is optional, it's for embedding hosts that can dup2 the
console output over a port.

If you're still having problems, I suggest you inspect open ports and
check the debugger is actually listening on the correct interface and
port, and that the debuggee can reach it.

-- 
Michael Hutchinson
http://mjhutchinson.com