[Mono-dev] Soft-debugger add-in problems
Hello Michael Hutchinson. I've been trying to implement a soft debugger for embedded mono. I googled it several times and only found your answers (on different websites). Your posts always said the same thing: Develop a debugger add-in to MonoDevelop. I've been trying to implement that but Moonlight soft debugger is a complex piece of code. Can you write a simple tutorial about the subject? Or send me a sample code? Or at least, give me some more clues so I can write a simple tutorial? Thanks in advance. Huseyin, revantheda...@gmail.com ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Soft Debugger issues (can't suspend threads in wait_for_suspend)
Turns out it might be due to Win32 limitations (QueueUserAPC works only if SleepEx/WaitForMultipleObjectsEx etc... are used), as notify_thread_apc is never called back. I can fix that on my own threads. However, finalizer thread should use such functions as well otherwise it will always hang internally. What version of mono are you using? I believe this was fixed several months ago in the 2.6 and later branches. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Soft Debugger issues (can't suspend threads in wait_for_suspend)
I am having trouble with mono soft debugger. - I embed Mono runtime in my program, and I got MonoDevelop to act as SoftDebugger client - Mono soft debugger is loading properly (first breakpoint usually works -- if already set beforehand -- I can see callstacks, etc...) - As soon as I press F5 -- to execute until this breakpoint is reached again next iteration -- or if I disable/reenable this breakpoint, program hang (see log) - Main loop is in C and Mono functions are called regularly. I traced down the problem to thread(s) not suspending (cf log). Usually, it seems it is the Finalizer thread (in this case 2054) that doesn't get suspended. In mono sources, I tried to call mono_gc_collect/mono_gc_invoke_finalizers in the suspend_thread loop. In that case, I can manage to have F5 working (breakpoint trigger every step inside the loop). However it doesn't work as soon as I do anything else (such as removing adding again the breakpoint). I remember seeing this problem on more than 1 thread when I had other threads active (i.e. Waiting for 3(4) threads to suspend...) Does anyone have an idea? Maybe there is something special to do if Mono doesn't keep hand (often back to full unmanaged world since main loop is in C) Debugger log: [0410] Thread started, obj=04702F20, tls=004CDA60. [0410] Suspended. [0410] Resumed. [0410] Suspending vm... [0410] Sent event VM_START, suspend=2. [0410] Suspended. [dbg] Agent thread started, pid=1260 [2054] Thread started, obj=04702E70, tls=004EC1D8. Finalizer thread [2054] Suspended. [dbg] Received command VM(VERSION), id=1. [dbg] Received command VM(SET_PROTOCOL_VERSION), id=2. [dbg] Protocol version 2.2, client protocol version 2.2. [dbg] Received command APPDOMAIN(1), id=3. ... [0410] Suspended. [dbg] Received command TYPE(1), id=1785. [dbg] Received command TYPE(6), id=1786. [2054] Received single step event for suspending. [2054] Suspended. [dbg] Received command VM(RESUME), id=1787. [1260] Resuming vm... [2054] Resumed. [0410] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1788. [dbg] Received command TYPE(6), id=1789. [2054] Received single step event for suspending. [2054] Suspended. [dbg] Received command VM(RESUME), id=1790. [1260] Resuming vm... [2054] Resumed. [0410] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1791. [dbg] Received command TYPE(6), id=1792. [dbg] Received command VM(RESUME), id=1793. [2054] Received single step event for suspending. [2054] Suspended. [1260] Resuming vm... [0410] Resumed. [2054] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1794. [dbg] Received command TYPE(6), id=1795. [dbg] Received command VM(RESUME), id=1796. [1260] Resuming vm... [0410] Resumed. [0410] Breakpoint hit, method=Step, offset=0x1e. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event BREAKPOINT, suspend=2. [0410] Suspended. [dbg] Received command VM(ALL_THREADS), id=1797. [dbg] Received command THREAD(1), id=1798. Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Soft Debugger issues (can't suspend threads in wait_for_suspend)
Just as a small addition, to confirm what I said earlier concerning situation with additional threads. After adding 2 threads that don't actually call mono (simply register them with mono_thread_attach(mono_get_root_domain())), I end up having: Waiting for 2(4) threads to suspend... which mean 1 of the fully native threads is also blocking it. Maybe it can't detect well when threads are running in native mode? I will continue to investigate as well. On Wed, Jan 26, 2011 at 12:58 AM, Virgile Bello virgile.be...@gmail.comwrote: I am having trouble with mono soft debugger. - I embed Mono runtime in my program, and I got MonoDevelop to act as SoftDebugger client - Mono soft debugger is loading properly (first breakpoint usually works -- if already set beforehand -- I can see callstacks, etc...) - As soon as I press F5 -- to execute until this breakpoint is reached again next iteration -- or if I disable/reenable this breakpoint, program hang (see log) - Main loop is in C and Mono functions are called regularly. I traced down the problem to thread(s) not suspending (cf log). Usually, it seems it is the Finalizer thread (in this case 2054) that doesn't get suspended. In mono sources, I tried to call mono_gc_collect/mono_gc_invoke_finalizers in the suspend_thread loop. In that case, I can manage to have F5 working (breakpoint trigger every step inside the loop). However it doesn't work as soon as I do anything else (such as removing adding again the breakpoint). I remember seeing this problem on more than 1 thread when I had other threads active (i.e. Waiting for 3(4) threads to suspend...) Does anyone have an idea? Maybe there is something special to do if Mono doesn't keep hand (often back to full unmanaged world since main loop is in C) Debugger log: [0410] Thread started, obj=04702F20, tls=004CDA60. [0410] Suspended. [0410] Resumed. [0410] Suspending vm... [0410] Sent event VM_START, suspend=2. [0410] Suspended. [dbg] Agent thread started, pid=1260 [2054] Thread started, obj=04702E70, tls=004EC1D8. Finalizer thread [2054] Suspended. [dbg] Received command VM(VERSION), id=1. [dbg] Received command VM(SET_PROTOCOL_VERSION), id=2. [dbg] Protocol version 2.2, client protocol version 2.2. [dbg] Received command APPDOMAIN(1), id=3. ... [0410] Suspended. [dbg] Received command TYPE(1), id=1785. [dbg] Received command TYPE(6), id=1786. [2054] Received single step event for suspending. [2054] Suspended. [dbg] Received command VM(RESUME), id=1787. [1260] Resuming vm... [2054] Resumed. [0410] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1788. [dbg] Received command TYPE(6), id=1789. [2054] Received single step event for suspending. [2054] Suspended. [dbg] Received command VM(RESUME), id=1790. [1260] Resuming vm... [2054] Resumed. [0410] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1791. [dbg] Received command TYPE(6), id=1792. [dbg] Received command VM(RESUME), id=1793. [2054] Received single step event for suspending. [2054] Suspended. [1260] Resuming vm... [0410] Resumed. [2054] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1794. [dbg] Received command TYPE(6), id=1795. [dbg] Received command VM(RESUME), id=1796. [1260] Resuming vm... [0410] Resumed. [0410] Breakpoint hit, method=Step, offset=0x1e. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event BREAKPOINT, suspend=2. [0410] Suspended. [dbg] Received command VM(ALL_THREADS), id=1797. [dbg] Received command THREAD(1), id=1798. Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Soft Debugger issues (can't suspend threads in wait_for_suspend)
Sorry, last small update, if I simply disable the waiting loop in wait_for_suspend() and make is_suspended() always return TRUE, breakpoints/tracing work as expected (except maybe playing with other threads of course). This seems to confirm there might be some false positive when trying to detect threads that run in native mode (mono think they are managed). On Wed, Jan 26, 2011 at 1:06 AM, Virgile Bello virgile.be...@gmail.comwrote: Just as a small addition, to confirm what I said earlier concerning situation with additional threads. After adding 2 threads that don't actually call mono (simply register them with mono_thread_attach(mono_get_root_domain())), I end up having: Waiting for 2(4) threads to suspend... which mean 1 of the fully native threads is also blocking it. Maybe it can't detect well when threads are running in native mode? I will continue to investigate as well. On Wed, Jan 26, 2011 at 12:58 AM, Virgile Bello virgile.be...@gmail.comwrote: I am having trouble with mono soft debugger. - I embed Mono runtime in my program, and I got MonoDevelop to act as SoftDebugger client - Mono soft debugger is loading properly (first breakpoint usually works -- if already set beforehand -- I can see callstacks, etc...) - As soon as I press F5 -- to execute until this breakpoint is reached again next iteration -- or if I disable/reenable this breakpoint, program hang (see log) - Main loop is in C and Mono functions are called regularly. I traced down the problem to thread(s) not suspending (cf log). Usually, it seems it is the Finalizer thread (in this case 2054) that doesn't get suspended. In mono sources, I tried to call mono_gc_collect/mono_gc_invoke_finalizers in the suspend_thread loop. In that case, I can manage to have F5 working (breakpoint trigger every step inside the loop). However it doesn't work as soon as I do anything else (such as removing adding again the breakpoint). I remember seeing this problem on more than 1 thread when I had other threads active (i.e. Waiting for 3(4) threads to suspend...) Does anyone have an idea? Maybe there is something special to do if Mono doesn't keep hand (often back to full unmanaged world since main loop is in C) Debugger log: [0410] Thread started, obj=04702F20, tls=004CDA60. [0410] Suspended. [0410] Resumed. [0410] Suspending vm... [0410] Sent event VM_START, suspend=2. [0410] Suspended. [dbg] Agent thread started, pid=1260 [2054] Thread started, obj=04702E70, tls=004EC1D8. Finalizer thread [2054] Suspended. [dbg] Received command VM(VERSION), id=1. [dbg] Received command VM(SET_PROTOCOL_VERSION), id=2. [dbg] Protocol version 2.2, client protocol version 2.2. [dbg] Received command APPDOMAIN(1), id=3. ... [0410] Suspended. [dbg] Received command TYPE(1), id=1785. [dbg] Received command TYPE(6), id=1786. [2054] Received single step event for suspending. [2054] Suspended. [dbg] Received command VM(RESUME), id=1787. [1260] Resuming vm... [2054] Resumed. [0410] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1788. [dbg] Received command TYPE(6), id=1789. [2054] Received single step event for suspending. [2054] Suspended. [dbg] Received command VM(RESUME), id=1790. [1260] Resuming vm... [2054] Resumed. [0410] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1791. [dbg] Received command TYPE(6), id=1792. [dbg] Received command VM(RESUME), id=1793. [2054] Received single step event for suspending. [2054] Suspended. [1260] Resuming vm... [0410] Resumed. [2054] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1794. [dbg] Received command TYPE(6), id=1795. [dbg] Received command VM(RESUME), id=1796. [1260] Resuming vm... [0410] Resumed. [0410] Breakpoint hit, method=Step, offset=0x1e. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event BREAKPOINT, suspend=2. [0410] Suspended. [dbg] Received command VM(ALL_THREADS), id=1797. [dbg] Received command THREAD(1), id=1798. Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... Waiting for 1(2) threads to suspend... ___
Re: [Mono-dev] Soft Debugger issues (can't suspend threads in wait_for_suspend)
Turns out it might be due to Win32 limitations (QueueUserAPC works only if SleepEx/WaitForMultipleObjectsEx etc... are used), as notify_thread_apc is never called back. I can fix that on my own threads. However, finalizer thread should use such functions as well otherwise it will always hang internally. Sorry for the trouble. On Wed, Jan 26, 2011 at 1:26 AM, Virgile Bello virgile.be...@gmail.comwrote: Sorry, last small update, if I simply disable the waiting loop in wait_for_suspend() and make is_suspended() always return TRUE, breakpoints/tracing work as expected (except maybe playing with other threads of course). This seems to confirm there might be some false positive when trying to detect threads that run in native mode (mono think they are managed). On Wed, Jan 26, 2011 at 1:06 AM, Virgile Bello virgile.be...@gmail.comwrote: Just as a small addition, to confirm what I said earlier concerning situation with additional threads. After adding 2 threads that don't actually call mono (simply register them with mono_thread_attach(mono_get_root_domain())), I end up having: Waiting for 2(4) threads to suspend... which mean 1 of the fully native threads is also blocking it. Maybe it can't detect well when threads are running in native mode? I will continue to investigate as well. On Wed, Jan 26, 2011 at 12:58 AM, Virgile Bello virgile.be...@gmail.comwrote: I am having trouble with mono soft debugger. - I embed Mono runtime in my program, and I got MonoDevelop to act as SoftDebugger client - Mono soft debugger is loading properly (first breakpoint usually works -- if already set beforehand -- I can see callstacks, etc...) - As soon as I press F5 -- to execute until this breakpoint is reached again next iteration -- or if I disable/reenable this breakpoint, program hang (see log) - Main loop is in C and Mono functions are called regularly. I traced down the problem to thread(s) not suspending (cf log). Usually, it seems it is the Finalizer thread (in this case 2054) that doesn't get suspended. In mono sources, I tried to call mono_gc_collect/mono_gc_invoke_finalizers in the suspend_thread loop. In that case, I can manage to have F5 working (breakpoint trigger every step inside the loop). However it doesn't work as soon as I do anything else (such as removing adding again the breakpoint). I remember seeing this problem on more than 1 thread when I had other threads active (i.e. Waiting for 3(4) threads to suspend...) Does anyone have an idea? Maybe there is something special to do if Mono doesn't keep hand (often back to full unmanaged world since main loop is in C) Debugger log: [0410] Thread started, obj=04702F20, tls=004CDA60. [0410] Suspended. [0410] Resumed. [0410] Suspending vm... [0410] Sent event VM_START, suspend=2. [0410] Suspended. [dbg] Agent thread started, pid=1260 [2054] Thread started, obj=04702E70, tls=004EC1D8. Finalizer thread [2054] Suspended. [dbg] Received command VM(VERSION), id=1. [dbg] Received command VM(SET_PROTOCOL_VERSION), id=2. [dbg] Protocol version 2.2, client protocol version 2.2. [dbg] Received command APPDOMAIN(1), id=3. ... [0410] Suspended. [dbg] Received command TYPE(1), id=1785. [dbg] Received command TYPE(6), id=1786. [2054] Received single step event for suspending. [2054] Suspended. [dbg] Received command VM(RESUME), id=1787. [1260] Resuming vm... [2054] Resumed. [0410] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1788. [dbg] Received command TYPE(6), id=1789. [2054] Received single step event for suspending. [2054] Suspended. [dbg] Received command VM(RESUME), id=1790. [1260] Resuming vm... [2054] Resumed. [0410] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1791. [dbg] Received command TYPE(6), id=1792. [dbg] Received command VM(RESUME), id=1793. [2054] Received single step event for suspending. [2054] Suspended. [1260] Resuming vm... [0410] Resumed. [2054] Resumed. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event TYPE_LOAD, suspend=2. [0410] Suspended. [dbg] Received command TYPE(1), id=1794. [dbg] Received command TYPE(6), id=1795. [dbg] Received command VM(RESUME), id=1796. [1260] Resuming vm... [0410] Resumed. [0410] Breakpoint hit, method=Step, offset=0x1e. [0410] Suspending vm... [0410] Interrupting 2054... [0410] Sent event BREAKPOINT, suspend=2. [0410] Suspended. [dbg] Received command VM(ALL_THREADS), id=1797. [dbg] Received command THREAD(1), id=1798. Waiting for 1(2) threads to suspend... Waiting
[Mono-dev] soft debugger
Hi there, On which platforms is the soft debugger supported? Thanks, pablo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] soft debugger
On amd64/x86/arm. Zoltan On Sun, Feb 21, 2010 at 11:10 PM, pablosantosl...@terra.es pablosantosl...@terra.es wrote: Hi there, On which platforms is the soft debugger supported? Thanks, pablo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] soft debugger
on every OS or just Linux?? I know it's on Mac too, we're using it! :-) On 21/02/2010 23:15, Zoltan Varga wrote: On amd64/x86/arm. Zoltan On Sun, Feb 21, 2010 at 11:10 PM, pablosantosl...@terra.es mailto:pablosantosl...@terra.es pablosantosl...@terra.es mailto:pablosantosl...@terra.es wrote: Hi there, On which platforms is the soft debugger supported? Thanks, pablo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com mailto:Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] soft debugger
Hi, It is known to work on linux, windows, mac and the iphone. Zoltan On Sun, Feb 21, 2010 at 11:52 PM, pablosantosl...@terra.es pablosantosl...@terra.es wrote: on every OS or just Linux?? I know it's on Mac too, we're using it! :-) On 21/02/2010 23:15, Zoltan Varga wrote: On amd64/x86/arm. Zoltan On Sun, Feb 21, 2010 at 11:10 PM, pablosantosl...@terra.es mailto:pablosantosl...@terra.es pablosantosl...@terra.es mailto:pablosantosl...@terra.es wrote: Hi there, On which platforms is the soft debugger supported? Thanks, pablo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com mailto:Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Soft Debugger Patch for Windows
Hi, Looks ok. Zoltan On Tue, Nov 10, 2009 at 3:49 PM, Jonathan Chambers jonc...@gmail.comwrote: Hello, Attached is a patch for supporting the soft debugger on Windows. The biggest changes IMO are not to the debugger, but to the mono-* synchronization utilities. The semaphores for example, will be used is other places in the runtime since MONO_HAS_SEMAPHORES is now defined. I'd like some input in this area. Also, all the utilities are currently done as macros. It seemed they might easier be done as functions, especially the not quite working conditional variables since there is no direct equivalent in Win32 (until Vista). FYI, these changes let me run 40/45 on the soft debugger unit tests, and I could debug using MD on Windows as well. Thanks, Jonathan ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Soft debugger HOWTO
Hi, After the announcement last week of the new soft debugger, I have several questions: - I understand MD is the primary interface *right now* for the soft debugger, is it possible to debug a Linux app too? - Is there any other available interface to use the soft debugger besides MD? - As Miguel pointed to me last week, the new softdeb will allow debuggin gon any platform, I don't know if anyone experienced it yet (I'll definitely give it a try asap), if so, any feedback? I know it's still a little bit too soon, but once the softdeb gets some good visibility, I honestly trust we're about to see a huge change in the way Mono is used. pablo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Soft debugger HOWTO
On 9-Nov-09, at 6:11 PM, pablosantosl...@terra.es wrote: Hi, After the announcement last week of the new soft debugger, I have several questions: - I understand MD is the primary interface *right now* for the soft debugger, is it possible to debug a Linux app too? You mean a native app? No. You mean a mono app on linux? Yes, on x86 and amd64 and arm currently. - Is there any other available interface to use the soft debugger besides MD? You can create any interface you like on top of the Mono.Debugger.Soft.dll, MonoDevelop is the interface we support. - As Miguel pointed to me last week, the new softdeb will allow debuggin gon any platform, I don't know if anyone experienced it yet (I'll definitely give it a try asap), if so, any feedback? We currently have it ported to: - linux (x86, amd64, arm, arm-full-aot) - darwin (x86, arm, arm-full-aot) The point miguel was making is that porting to new architectures is a minor (1 day) task in most cases. For example, Jonathan Chambers has it mostly ported to win32 already -g ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Soft debugger HOWTO
Hi Geoff, - I understand MD is the primary interface *right now* for the soft debugger, is it possible to debug a Linux app too? You mean a native app? No. You mean a mono app on linux? Yes, on x86 and amd64 and arm currently. I'm only concerned 99.99% of the time about managed code. So that's what I need. - Is there any other available interface to use the soft debugger besides MD? You can create any interface you like on top of the Mono.Debugger.Soft.dll, MonoDevelop is the interface we support. Will it make sense to have some sort of command line interface? Maybe not, MD will always be better... - As Miguel pointed to me last week, the new softdeb will allow debuggin gon any platform, I don't know if anyone experienced it yet (I'll definitely give it a try asap), if so, any feedback? We currently have it ported to: - linux (x86, amd64, arm, arm-full-aot) - darwin (x86, arm, arm-full-aot) The point miguel was making is that porting to new architectures is a minor (1 day) task in most cases. Excellent! ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Soft debugger HOWTO
On 9-Nov-09, at 6:33 PM, pablosantosl...@terra.es wrote: - Is there any other available interface to use the soft debugger besides MD? You can create any interface you like on top of the Mono.Debugger.Soft.dll, MonoDevelop is the interface we support. Will it make sense to have some sort of command line interface? Maybe not, MD will always be better... We have no plans to make a command line interface, someone from the community is free to do so. Our suggested and supported interface is going to be MonoDevelop -g ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
