[Mono-bugs] [Bug 573750] New: -noregistrar required

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=573750

http://bugzilla.novell.com/show_bug.cgi?id=573750#c0


           Summary: -noregistrar required
    Classification: Mono
           Product: Mono: Runtime
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: interop
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: zach.griswold at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Community User
           Blocker: No


Created an attachment (id=338738)
 --> (http://bugzilla.novell.com/attachment.cgi?id=338738)
Sample MonoTouch/XCode Project for replication.

Synopsis:

The "-noregistrar" flag seems to be required whenever I use bindings and need
to link with a static library. The project works fine in the simulator then
crashes on the device (with a SIGBUS signal). Using the "-noregistrar" flag
fixes this issue. This has happened on three different equations (with an
internal library I use, with the sample I'm attaching, and with my MTCocos2D
project on Google Code). I've heard of other people having the same issue
(linking with static library) and the "-noregistrar" flag fixing the problem
for them too. This problem occurs with both fat (ARM + x86) and "normal" static
libraries. Also, optimization/THUMB/symbol flags for compiling the static
library seem to have no effect on this issue.

Affects: All generations of iPod Touch/iPhone devices
OSes Tested: OS 3.0, 3.1, 3.1.2
Development Machine: MBP 4.1 OS X 10.6
Using the sample: You should just be able to run the sample on the device and
see that the project works. Remove the "-noregistrar" from the build settings
and re-run on the device and you should see it crash with a SIGBUS failure.

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.