Bug 47053 - bug-45841-fpstack-exceptions.exe fails on osx64.
Summary: bug-45841-fpstack-exceptions.exe fails on osx64.
Status: CLOSED FIXED
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Vladimir Kargov
URL:
Depends on:
Blocks:
 
Reported: 2016-11-15 21:03 UTC by Zoltan Varga
Modified: 2017-06-29 01:52 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
CLOSED FIXED

Description Zoltan Varga 2016-11-15 21:03:59 UTC
This is a tracking bug so the test can be disabled so we have green builds again.
Comment 1 Vladimir Kargov 2017-03-07 02:34:40 UTC
The benchmark works with the upstream runtime. I'll re-enable it in the testing suite.
Comment 2 Rodrigo Kumpera 2017-05-24 18:15:54 UTC
ping
Comment 3 Vladimir Kargov 2017-06-06 22:18:14 UTC
The test leads to a segfault on certain mac x64 machines due to this fragment calling the constructor with incorrect argumetns:
        ldc.r8 5
        newobj     instance void [mscorlib]System.OverflowException::.ctor(string)

The runtime correctly identifies the problem when run with --security=verifiable.

I'll submit a fix for the test case shortly.

Is there an issue with the runtime crashing on that code, though?
Comment 4 Vladimir Kargov 2017-06-29 01:52:35 UTC
Fixed by https://github.com/mono/mono/pull/4927