[Mono-dev] (no subject)

Greg Young gregoryyoung1 at gmail.com
Mon Jan 13 09:25:22 UTC 2014


As expected (totally predictable) its officially a heisenbug. Running with
gdb causes it to no longer fail.


On Fri, Jan 10, 2014 at 1:22 PM, "Andrés G. Aragoneses" <knocte at gmail.com>wrote:

> If it still crashes with master, run it with gdb and obtain a backtrace,
> and attach it to a bug report.
>
> On 10/01/14 11:43, James Nugent wrote:
> > Thanks, I'll try this today.
> >
> > Cheers,
> >
> >
> > James
> >
> >> On 10 Jan 2014, at 10:42, "Andrés G. Aragoneses" <knocte at gmail.com>
> wrote:
> >>
> >> This 64bits-only bug could be the culprit:
> >>
> >> https://bugzilla.xamarin.com/show_bug.cgi?id=14834
> >>
> >> It's fixed already in master branch. Try master.
> >>
> >>> On 10/01/14 11:34, "Andrés G. Aragoneses" wrote:
> >>> What version of mono, and what architecture are you running this on?
> >>>
> >>>> On 07/01/14 16:20, Greg Young wrote:
> >>>> Interesting issue came up today. All code works fine when run with
> mono
> >>>> regularly. However when we statically link mono and put the system
> under
> >>>> pressure we end up getting a SIGABRT on a fairly innocuous call (not
> >>>> right away). We cannot reproduce this with mono not statically linked.
> >>>> Anyone have any ideas where to start looking?
> >>>>
> >>>> at <unknown> <0xffffffff>
> >>>> at (wrapper managed-to-native)
> >>>> object.__icall_wrapper_mono_array_new_specific (intptr,int)
> <0xffffffff>
> >>>> at System.IO.MemoryStream.set_Capacity (int) <0x00077>
> >>>> at System.IO.MemoryStream.Expand (int) <0x00036>
> >>>> at System.IO.MemoryStream.Write (byte[],int,int) <0x00093>
> >>>>
> >>>> at ProtoBuf.ProtoWriter.Flush (ProtoBuf.ProtoWriter) <0x00034>
> >>>> at ProtoBuf.ProtoWriter.Dispose () <0x0001b>
> >>>> at ProtoBuf.ProtoWriter.Close () <0x00023>
> >>>> at ProtoBuf.Meta.TypeModel.Serialize
> >>>> (System.IO.Stream,object,ProtoBuf.SerializationContext) <0x00087>
> >>>> at ProtoBuf.Meta.TypeModel.Serialize (System.IO.Stream,object)
> <0x0001b>
> >>>> at ProtoBuf.Serializer.Serialize<T> (System.IO.Stream,T) <0x00037>
> >>>> at
> >>>> EventStore.Core.Services.Transport.Tcp.ProtobufExtensions.Serialize<T>
> >>>> (T) <0x00073>
> >>>> at
> >>>>
> EventStore.Core.Services.Transport.Tcp.InternalTcpDispatcher.WrapDataChunkBulk
> >>>> (EventStore.Core.Messages.ReplicationMessage/DataChunkBulk) <0x00153>
> >>>>
> >>>> at (wrapper delegate-invoke)
> >>>>
> System.Func`2<EventStore.Core.Messages.ReplicationMessage/DataChunkBulk,
> >>>>
> EventStore.Core.Services.Transport.Tcp.TcpPackage>.invoke_TResult__this___T
> >>>> (EventStore.Core.Message
> >>>>
> >>>> s.ReplicationMessage/DataChunkBulk) <0xffffffff>
> >>>> at
> >>>>
> EventStore.Core.Services.Transport.Tcp.TcpDispatcher/<AddWrapper>c__AnonStorey4D`1.<>m__10A
> >>>> (EventStore.Core.Messaging.Message) <0x00057>
> >>>>
> >>>> at (wrapper delegate-invoke)
> >>>> System.Func`2<EventStore.Core.Messaging.Message,
> >>>>
> EventStore.Core.Services.Transport.Tcp.TcpPackage>.invoke_TResult__this___T
> >>>> (EventStore.Core.Messaging.Message) <0xffffffff>
> >>>>
> >>>> at EventStore.Core.Services.Transport.Tcp.TcpDispatcher.WrapMessage
> >>>> (EventStore.Core.Messaging.Message) <0x000d6>
> >>>> at
> >>>>
> EventStore.Core.Services.Transport.Tcp.TcpConnectionManager.SendMessage
> >>>> (EventStore.Core.Messaging.Message) <0x0004c>
> >>>>
> >>>> at EventStore.Core.Services.TcpSendService.Handle
> >>>> (EventStore.Core.Messages.TcpMessage/TcpSend) <0x0001f>
> >>>> at EventStore.Core.Bus.MessageHandler`1.TryHandle
> >>>> (EventStore.Core.Messaging.Message) <0x00094>
> >>>>
> >>>> at EventStore.Core.Bus.InMemoryBus.Publish
> >>>> (EventStore.Core.Messaging.Message) <0x000fe>
> >>>> at EventStore.Core.Bus.InMemoryBus.Handle
> >>>> (EventStore.Core.Messaging.Message) <0x00013>
> >>>>
> >>>> at EventStore.Core.Bus.QueuedHandlerThreadPool.ReadFromQueue (object)
> >>>> <0x00137>
> >>>> at (wrapper runtime-invoke)
> <Module>.runtime_invoke_void__this___object
> >>>> (object,intptr,intptr,intptr) <0xffffffff>
> >>>>
> >>>>
> >>>> Native stacktrace:
> >>>>
> >>>> ./clusternode() [0x6215be]
> >>>>
> >>>> /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7f289d4f2cb0]
> >>>> /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f289d159425]
> >>>>
> >>>> /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7f289d15cb8b]
> >>>> ./clusternode() [0x5803dd]
> >>>> ./clusternode() [0x580472]
> >>>> ./clusternode() [0x524a24]
> >>>> ./clusternode() [0x528c0e]
> >>>> ./clusternode() [0x52cf61]
> >>>> ./clusternode() [0x52e541]
> >>>> ./clusternode() [0x51283f]
> >>>> ./clusternode() [0x5186b3]
> >>>> ./clusternode() [0x518c6b]
> >>>> ./clusternode() [0x50b487]
> >>>> ./clusternode() [0x50b6d8]
> >>>> ./clusternode(mono_array_new_specific+0x36) [0x4e4256]
> >>>> [0x41e25187]
> >>>>
> >>>> Debug info from gdb:
> >>>>
> >>>>
> >>>> =================================================================
> >>>>
> >>>> Got a SIGABRT while executing native code. This usually indicates
> >>>> a fatal error in the mono runtime or one of the native libraries
> >>>> used by your application.
> >>>> =================================================================
> >>>>
> >>>> Aborted
> >>>>
> >>>>
> >>>> --
> >>>> Le doute n'est pas une condition agréable, mais la certitude est
> absurde.
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Mono-devel-list mailing list
> >>>> Mono-devel-list at lists.ximian.com
> >>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >>
> >>
> >> _______________________________________________
> >> Mono-devel-list mailing list
> >> Mono-devel-list at lists.ximian.com
> >> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>



-- 
Le doute n'est pas une condition agréable, mais la certitude est absurde.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140113/e9bcb90e/attachment.html>


More information about the Mono-devel-list mailing list