You might be able to run monodevelop on your desktop machine and then
remote debug on the headless server (see
https://ebsteblog.wordpress.com/2013/12/04/remote-debugging-with-monodevelop/
for some instructions).
Chris
Swiedler wrote on 2015-11-15 at 17:03 +0100:
> Do you mean for development, o
Do you mean for development, or for debugging? The application is running on a
headless server and I can’t run monodevelop or Xamarin on it. I’m building the
exes with the mono toolchain under Windows, by installing it as a .net profile.
chris
> On Nov 14, 2015, at 6:32 PM, Edward Ned Harvey (m
> From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
> boun...@lists.ximian.com] On Behalf Of Chris Swiedler
>
> We have a server application that's being developed under Visual Studio and
> run under Mono 3.12. We're generating .mdb files from the .pdbs that VS
> creates. Wit
Hi,
The gdb support for mono might work only if the program is started from
gdb, not when it is attached to. If you aot your assemblies (see the mono
man page), the aot compiler generates debug info which gdb can read, so you
should get better stack traces. About the "../../gdb/dwarf2-frame.c:68
We have a server application that's being developed under Visual Studio and run
under Mono 3.12. We're generating .mdb files from the .pdbs that VS creates.
With those deployed next to the executable, mono will give full callstacks with
source and line information when logging exceptions, so I b
