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)

See Also:
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

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.

Note You need to log in before you can comment on or make changes to this bug.