On Friday, 10 January 2014 at 18:17:17 UTC, Alexander Bothe wrote:
On Friday, 10 January 2014 at 18:14:04 UTC, Daniel Kozák wrote:
Now it works :), thanks a lot
Finally! :)
Confirmed working for me as well! Thanks for working with us to
iron this out. I think this will help a lot of people
On Wednesday, 8 January 2014 at 14:30:50 UTC, Alexander Bothe
wrote:
On Wednesday, 8 January 2014 at 12:35:47 UTC, Daniel Kozak
wrote:
I do not think so because it runs gdb, and it stops on break
point, but it does not show it properly on monodevelop editor
(red marker is not mark as current
On Thursday, 9 January 2014 at 19:20:35 UTC, Daniel Kozak wrote:
So I really do not know, what is wrong with my monodevelop.
Anyway with patched gdb (https://github.com/ibuclaw/gdb) and
normal GDB plugin I can debbug my application quiet well.
Just set this up, and the regular GDB plugin with
On Thursday, 9 January 2014 at 23:15:12 UTC, Alexander Bothe
wrote:
On Thursday, 9 January 2014 at 22:50:09 UTC, Daniel Kozak wrote:
On Thursday, 9 January 2014 at 21:47:40 UTC, Alexander Bothe
wrote:
So btw, could you please define 'does not work'? Is there an
exception, is there just a
On a hunch that maybe it has to do with some strange assembly
version or mono version mismatch, I used monodis/ilasm to
roundtrip the assembly, reassembling it against the dependencies
provided in the git repo. It still exhibits the same breakpoint
issue, so something is the code itself must
On Friday, 10 January 2014 at 02:33:05 UTC, Jameson Ernst wrote:
Since recompiling from source fixes the problem, this is
difficult to test. However, since I've successfully
roundtripped the broken dll, I can try to find and set that
value in the IL itself. My IL knowledge is a bit rusty
On Friday, 10 January 2014 at 03:29:06 UTC, Alexander Bothe wrote:
On Friday, 10 January 2014 at 02:33:05 UTC, Jameson Ernst wrote:
On a hunch that maybe it has to do with some strange assembly
version or mono version mismatch, I used monodis/ilasm to
roundtrip the assembly, reassembling
