Hi,
I´ve seen that external process attachment is prio 2 on the feature list, so I´ll thought I give it a try. There are several reasons why you would need this, e.g., it saves time when starting up a server application externally and later attach to it with the debugger. Also it is the first step to remote and
native debugging.
It already works quite confidently unless to the point that I have
not been able to deactivate all outstanding steppers (mostly those that
the callstack pad/logic builds up when constructing Function()
representations ... I guess that these steppers just serve as a kind of
cleanup events. When the callstack or the thread pad are not activated,
detachment works as expected). Function-evals, I also left out for the
time being having not found any watches/expressions in SharpDevelop
code (I did not search very long, I admit).
Also, it is clear that the SharpDevelop debugger model (single debugger active associated to some solution/project) is not fully compatible to the "attach to whatever and then choose the debugger models you like to activate" paradigm used, e.g., in the CLR debugger or VS.NET
I used Mike Stalls blog as the prime source of information: http://blogs.msdn.com/jmstall/
I would be happy if you request the code (zip file containing a patch and a new folder with debugging dialogs) from me either by giving me a direct email address or allowing me to attach files to my postings here. I´ll surely sign the agreement if you plan to accept the code