Well, there isn't much I can do to avoid underlying mono bugs. Have you
reported it?
Marc
On 16 Oct 2013 05:07, ch...@ochsnet.com wrote:
I was using 668, but this is a mono bug with reading streams I confirmed
it with just reading from the stream myself.
Rather annoying, I updated to the
I haven't reported it yet. Getting gdb working with java is a kind of a
PITA. But I'll probably have to break down and do it.
Chris
On Tuesday, October 15, 2013 11:14:41 PM UTC-7, Marc Gravell wrote:
Well, there isn't much I can do to avoid underlying mono bugs. Have you
reported it?
So part of this is a mono bug, segfaults shouldn't be happening in managed
code period.
I'm embedding mono 3 in a java app and consistently get the following when
deserializing a simple protobuf message.
Stacktrace:
at unknown 0x
at (wrapper managed-to-native)
Firstly: exactly what version is this? There was a bug in 663 relating to
threading (and which only exhibited after extended usage) that was fixed in
something like 668. If you are using something = 663 and 668 then please
update and retry.
Marc
(protobuf-net)
On 15 Oct 2013 16:22,
I was using 668, but this is a mono bug with reading streams I confirmed it
with just reading from the stream myself.
Rather annoying, I updated to the latest mono 3 master because of a
threading bug that was fixed 2 weeks ago, now this:)
Chris
On Tuesday, October 15, 2013 10:45:46 AM UTC-7,
