Bug 10857 - [ARM] System.Data.SqlTypes.SqlDecimal Crash on constructor
Summary: [ARM] System.Data.SqlTypes.SqlDecimal Crash on constructor
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System (show other bugs)
Version: 2.10.x
Hardware: Other Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-03-03 15:26 UTC by Matteo Fabbri
Modified: 2013-04-11 11:44 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 for Bug 10857 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 Matteo Fabbri 2013-03-03 15:26:28 UTC
Platform: ARM A10 (Hackberry board)
SO: Linaro Ubuntu Server

System.TypeInitializationException
Message:An exception was thrown by the type initializer for System.Data.SqlTypes.SqlDecimal

StackTrace:
System.OverflowException: Can't convert to SqlDecimal, Out of range at System.Data.SqlTypes.SqlDecimal..ctor (Byte bPrecision, Byte bScale, Boolean fPositive, Int32 data1, Int32 data2, Int32 data3, Int32 data4) [0x00000] in <filename unknown>:0  at System.Data.SqlTypes.SqlDecimal..cctor () [0x00000] in <filename unknown>:0
  --- End of inner exception stack trace ---
 at System.Data.DataColumn..ctor (System.String columnName, System.Type dataType, System.String expr, MappingType type) [0x00000] in <filename unknown>:0
 at System.Data.DataColumn..ctor (System.String columnName, System.Type dataType) [0x00000] in <filename unknown>:0
 at System.Data.DataColumnCollection.Add (System.String columnName, System.Type type) [0x00000] in <filename unknown>:0


No problem observed on different platform or OS
Comment 1 mickeyf 2013-04-11 09:28:29 UTC
I believe this may be the same bug I encountered using npgsql on the BeagleBone:

I have an application that I am mostly developing on a desktop PC but with the intention that it run on a BeagleBone (ARM architechture). Code that runs on the x86 mono fails on the armel, throwing an exception when it hits Adapter.Fill. In both cases I'm running mono 2.10.8.1 on a Ubuntu 12.04 build, npgsql is 2.0.12.0.

Here's my stacktrace:

2013/04/10 13:30:49 System.TypeInitializationException() An exception was thrown by the type initializer for System.Data.SqlTypes.SqlDecimal
at System.Data.DataColumn..ctor (System.String columnName, System.Type dataType, System.String expr, MappingType type) [0x00000] in <filename unknown>:0
at System.Data.DataColumn..ctor (System.String columnName, System.Type dataType) [0x00000] in <filename unknown>:0
at System.Data.DataColumnCollection.Add (System.String columnName, System.Type type) [0x00000] in <filename unknown>:0
at Npgsql.NpgsqlDataReader.GetResultsetSchema () [0x00000] in <filename unknown>:0
at Npgsql.NpgsqlDataReader.GetSchemaTable () [0x00000] in <filename unknown>:0
at System.Data.Common.DataAdapter.BuildSchema (IDataReader reader, System.Data.DataTable table, SchemaType schemaType, MissingSchemaAction missingSchAction, MissingMappingAction missingMapAction, System.Data.Common.DataTableMappingCollection dtMapping) [0x00000] in <filename unknown>:0
at System.Data.Common.DataAdapter.BuildSchema (IDataReader reader, System.Data.DataTable table, SchemaType schemaType) [0x00000] in <filename unknown>:0
at System.Data.Common.DataAdapter.FillTable (System.Data.DataTable dataTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords, System.Int32& counter) [0x00000] in <filename unknown>:0
at System.Data.Common.DataAdapter.FillInternal (System.Data.DataSet dataSet, System.String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords) [0x00000] in <filename unknown>:0
at System.Data.Common.DataAdapter.Fill (System.Data.DataSet dataSet, System.String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords) [0x00000] in <filename unknown>:0
at System.Data.Common.DbDataAdapter.Fill (System.Data.DataSet dataSet, Int32 startRecord, Int32 maxRecords, System.String srcTable, IDbCommand command, CommandBehavior behavior) [0x00000] in <filename unknown>:0
at System.Data.Common.DbDataAdapter.Fill (System.Data.DataSet dataSet) [0x00000] in <filename unknown>:0
at Vigil.Public.Database.SQLDatabase.GetDataTable (System.String strSQL) [0x00000] in <filename unknown>:0
Comment 2 mickeyf 2013-04-11 11:44:35 UTC
This appears to be a direct result of Bug #7938.
#9452  is probably also due to #7938