Bug 44204 - Initializing a float array with a negative size throws incorrect exception
Summary: Initializing a float array with a negative size throws incorrect exception
Status: NEW
Alias: None
Product: Runtime
Classification: Mono
Component: JIT (show other bugs)
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-09-12 17:46 UTC by Brian Raderman
Modified: 2017-03-07 21:04 UTC (History)
4 users (show)

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


Attachments
Test program (685 bytes, text/plain)
2016-09-12 17:46 UTC, Brian Raderman
Details


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 for Bug 44204 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description Brian Raderman 2016-09-12 17:46:46 UTC
Created attachment 17422 [details]
Test program

We expect a System.OverflowException when initializing an array with a negative size.  Mono ends up throwing a System.OutOfMemoryException instead.  This only occurs on 64-bit Mono.
Comment 1 Zoltan Varga 2016-09-15 15:07:10 UTC
This is a 64 bit only problem, it happens because the JIT passes a 32 bit int to the managed allocator method which takes a native int, and we don't do sign extension.