Mono 1.9.1 crashes with native stacktrace whilst compiling XSP on AMD64

Bug #240671 reported by Jo Shields
4
Affects Status Importance Assigned to Milestone
mono (Debian)
Fix Released
Unknown
mono (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: mono

Mono 1.9.1 appears to contain a runtime bug which may cause crashes - one repeatable example is compiling XSP, which fails in the same place on many (but not all) AMD64 systems running Debian Sid or Ubuntu Intrepid:

      /usr/bin/mcs -r:System.Web.dll -t:library -out:codebehind1.dll codebehind1.cs
      Stacktrace:

        at Mono.CSharp.Tokenizer.Reset () <0xffffffff>
        at Mono.CSharp.Tokenizer.Reset () <0x0000d>
        at Mono.CSharp.Tokenizer..cctor () <0x000da>
        at (wrapper runtime-invoke) Mono.CSharp.Driver.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>
        at Mono.CSharp.CSharpParser..ctor (Mono.CSharp.SeekableStreamReader,Mono.CSharp.SourceFile,System.Collections.ArrayList) <0xffffffff>
        at Mono.CSharp.CSharpParser..ctor (Mono.CSharp.SeekableStreamReader,Mono.CSharp.SourceFile,System.Collections.ArrayList) <0x000bc>
        at Mono.CSharp.Driver.parse (Mono.CSharp.SourceFile) <0x001a9>
        at Mono.CSharp.Driver.ProcessFiles () <0x00078>
        at Mono.CSharp.Driver.MainDriver (string[]) <0x00440>
        at Mono.CSharp.Driver.Main (string[]) <0x00079>
        at (wrapper runtime-invoke) Mono.CSharp.Driver.runtime_invoke_int_string[] (object,intptr,intptr,intptr) <0xffffffff>

      Native stacktrace:

              /usr/bin/mono [0x532a3d]
              /usr/bin/mono [0x440d2d]
              /lib/libpthread.so.0 [0x2ad82c4d9a80]
              /lib/libc.so.6(memcpy+0x60) [0x2ad82c9e7f40]
              /usr/bin/mono(mono_breakpoint_clean_code+0x1b) [0x428a8b]
              /usr/bin/mono [0x4423cd]
              /usr/bin/mono [0x537592]
              [0x41973160]

      =================================================================
      Got a SIGSEGV while executing native code. This usually indicates
      a fatal error in the mono runtime or one of the native libraries
      used by your application.
      =================================================================

The attached dpatch fixes the problem.

Revision history for this message
Jo Shields (directhex) wrote :
Changed in mono:
status: Unknown → New
Changed in mono:
status: New → Fix Released
Revision history for this message
Jo Shields (directhex) wrote :

The latest Mono package in Debian fixes this problem. I'll look at a fresh merge when I get a moment.

Changed in mono:
assignee: nobody → directhex
status: New → In Progress
Revision history for this message
Jo Shields (directhex) wrote :
Changed in mono:
assignee: directhex → nobody
status: In Progress → Confirmed
Revision history for this message
Daniel Holbach (dholbach) wrote : Sponsor Request

Sebastian: can you please take a look at it?

Revision history for this message
Jo Shields (directhex) wrote :

2ubuntu1 fixed this. Thanks to Chris Cheney

Changed in mono:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.