Bug 12579 - BigInteger regression
Summary: BigInteger regression
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 6.3.x
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-06-06 13:33 UTC by Boris Scheiman
Modified: 2013-06-06 14:50 UTC (History)
2 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 Developer Community or GitHub 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:
RESOLVED FIXED

Description Boris Scheiman 2013-06-06 13:33:34 UTC
The following code throws an IndexOutOfRangeException, which was already fixed in Mono trunk 1 year ago: https://bugzilla.xamarin.com/show_bug.cgi?id=2761

new BigInteger(new byte[] {0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00}); // Or any amount of 0 bytes

Expected: BigInteger.Zero
Comment 1 Sebastien Pouliot 2013-06-06 14:41:21 UTC
It does not look like a regression. It looks like that patch was never backported to mono-2-10, on which Xamarin.iOS 6.2 is based.

OTOH if you're using 6.3.x (beta or alpha) then it should work fine (as a unit test was added and is executed on each of the builds).

Can you confirm which version you're using (the bug report states 6.3.x) ?

The easiest way to get exact version information is to use the "Xamarin Studio" menu, "About Xamarin Studio" item, "Show Details" button and copy/paste the version informations (you can use the "Copy Information" button).
Comment 2 Boris Scheiman 2013-06-06 14:43:30 UTC
Ah, my bad. I didn't change that combobox. 6.2.7.1.


Full output:

=== Xamarin Studio ===

Version 4.0.8 (build 2)
Installation UUID: 067536de-eaae-47b8-97a7-818f2e1895d4
Runtime:
	Mono 2.10.12 (mono-2-10/c9b270d)
	GTK 2.24.16
	GTK# (2.12.0.0)
	Package version: 210120000

=== Apple Developer Tools ===

Xcode 4.6.2 (2067.2)
Build 4H1003

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Xamarin.iOS ===

Version: 6.2.7.1 (Business Edition)
Hash: 947e664
Branch: 
Build date: 2013-30-05 18:02:40-0400

=== Xamarin.Android ===

Version: 4.6.7 (Business Edition)
Android SDK: /Users/bscheiman/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		4.0   (API level 14)
		4.0.3 (API level 15)
Java SDK: /usr

=== Build Information ===

Release ID: 400080002
Git revision: 0a09117dec1aed78c735ac46f7a50ae7d12f7a7a
Build date: 2013-05-16 19:36:29+0000
Xamarin addins: 78d0437c3f92ae13042f81e5fd9487e2c28d5fbc

=== Operating System ===

Mac OS X 10.8.3
Darwin Boriss-MacBook-Pro.local 12.3.0 Darwin Kernel Version 12.3.0
    Sun Jan  6 22:37:10 PST 2013
    root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64



B
Comment 3 Sebastien Pouliot 2013-06-06 14:50:30 UTC
No problem :) I just wanted to be sure nothing else was wrong.

Original fix was: 4be2945202c9f3b9ce71ff3232f25cb8b60cc4d1

Backported to mono-2-10: b867bb24b258aeb87dfd57e5b3dab1c35479d6d2
Backported to mobile-master: 86931074e7694391bc082e5dc37777b16d827e37
monotouch/master bumped in: d1b6f9216d00b0b0c7d3e0ed926828ca953540a8

It will be part of the next, non-hotfix, maintenance release of 6.2.x.