[Mono-bugs] [Bug 487780] New: Mono fails (SIGABRT) to build on Ubuntu 9.04/x86-64
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Mon Mar 23 11:05:38 EDT 2009
https://bugzilla.novell.com/show_bug.cgi?id=487780
Summary: Mono fails (SIGABRT) to build on Ubuntu 9.04/x86-64
Classification: Mono
Product: Mono: Runtime
Version: 2.2.x
Platform: x86-64
OS/Version: Ubuntu
Status: NEW
Severity: Critical
Priority: P5 - None
Component: debug
AssignedTo: martin at novell.com
ReportedBy: mike at trausch.us
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Created an attachment (id=281215)
--> (https://bugzilla.novell.com/attachment.cgi?id=281215)
glibc crash error
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.7)
Gecko/2009030516 Ubuntu/9.04 (jaunty) Firefox/3.0.7
Mono fails to build on Ubuntu Jaunty (version 9.04). It looks like it may be a
problem with new verification functionality in the system's C library, though
take that with a grain of salt—I don't know how to confirm that hypothesis at
the moment.
Reproducible: Always
Steps to Reproduce:
1. Install Ubuntu Jaunty
2. Install Mono's build-time dependencies on the system.
3. Attempt to build Mono (build order: libgdiplus, mono).
Actual Results:
When Mono reaches the point of building System.ServiceModel.dll, it receives a
SIGABRT, and GLibc prints a message stating:
*** glibc detected ***
/tmp/mono2-build.15892/monobuild/mono-2.2/mono/mini/mono: free(): invalid
pointer: 0x00002aaab047f768 ***
The invalid pointer is in the memory map at:
2aaab0000000-2aaab1421000 rw-p 2aaab0000000 00:00 0
(See attached log files for more detail.)
Expected Results:
Mono should have built successfully.
This is on an Ubuntu Jaunty 9.04 system, due to be released in about 1 month.
This is a hard, reproducible crash resulting in the failure of the runtime to
build. Sometimes, running the build a second time will result in a successful
build, but then it does not install correctly ("make install" fails).
Also, this bug may be incorrectly categorized. I wasn't able to find the
options that seemed appropriate when creating the bug, though that might just
be my fault...
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the mono-bugs
mailing list