[Pkg-mono-devel] Mono 2.10.3, 2.10.4 debian squeeze build issues

[Iain Lane]

On Wed, Aug 17, 2011 at 11:07:15AM +0100, Jo Shields wrote:
> On Tue, 2011-08-16 at 17:57 -0700, ignusin wrote:
> > I reinstalled Debian on my VPS, so it is "clean" at the moment. I have
> > downloaded mono (2.10.4) & xsp(2.10.2) sources and installed all the
> > dependencies to build the first two.
> > It builds, but when I run xsp4 on HelloWorld project - it crashes with the
> > same assertion:
> > 
> > 
> > # xsp4 --port 8000
> > xsp4
> > Listening on address: 0.0.0.0
> > Root directory: /opt/mono/
> > Listening on port: 8000 (non-secure)
> > Hit Return to stop the server.
> > * Assertion at threads.c:785, condition `start_delegate != NULL' not met
> > 
> > Stacktrace:
> > 
> > 
> > Native stacktrace:
> > 
> >         /usr/bin/mono() [0x80ddbe9]
> >         [0x718440]
> >         /lib/i686/cmov/libc.so.6(abort+0x182) [0x13db82]
> >         /usr/bin/mono() [0x8220956]
> >         /usr/bin/mono() [0x82209d5]
> >         /usr/bin/mono() [0x814d908]
> >         /usr/bin/mono() [0x8207e9f]
> >         /usr/bin/mono() [0x822a756]
> >         /lib/i686/cmov/libpthread.so.0(+0x5955) [0x9e3955]
> >         /lib/i686/cmov/libc.so.6(clone+0x5e) [0x1dbe7e]
> > 
> > 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
> > 
> > 
> > I also tried to install it from experimental repository, but it has unmet
> > dependencies with libc6 (experimental packages require libc6 >= 2.13, but
> > 2.11.2-10 is installed).
> > 
> > Mono 2.10.1 however works fine when run XSP with the same project.
> 
> The good news is, we can reproduce this (on i386 Ubuntu Oneiric only).
> It's now being worked on.

The bad news is that we can't manage to reproduce this on any hardware
we actually have access to.

Would it be possible to give us an account on the box for debugging (I
can mail you an SSH public key)? If so, how did you produce the initial
/build/ failure? Did you download the mono package from experimental and
try to rebuild it under squeeze?  What command did you execute to do
this?

Regards,

-- 
Iain Lane                                  [ iain at orangesquash.org.uk ]
Debian Developer                                   [ laney at debian.org ]
Ubuntu Developer                                   [ laney at ubuntu.com ]
PhD student                                       [ ial at cs.nott.ac.uk ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-mono-devel/attachments/20110818/cf3d5790/attachment.pgp>