Bug 5487 - Running sample code from another problem (w/ DataGrid) report causes _crash_ due to bad indexing.
Summary: Running sample code from another problem (w/ DataGrid) report causes _crash_ ...
Alias: None
Product: Class Libraries
Classification: Mono
Component: Windows.Forms ()
Version: 2.10.x
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-06-03 17:36 UTC by Robert Wilkens
Modified: 2012-06-18 17:02 UTC (History)
2 users (show)

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:

Description Robert Wilkens 2012-06-03 17:36:22 UTC
Description of Problem:
This bug report has the sample code

When i run that sample code, if i click on the row header, it crashes with an index out of range exception.

Steps to reproduce the problem:
1. Run the code from that bug report
2. Click the row header (on left)
3. In Windows/.net it works fine.
4. In Linux/mono it crashes with an index out of range exception

Actual Results:

Expected Results:

How often does this happen? 
Every time

Additional Information:
I've actually already submitted a fix for this.  The bug report is a formality.
Comment 1 Thomas Goldstein 2012-06-18 16:40:04 UTC
Patch applied (commit 42ebb31fc143a171a6a5930bc647627c557842ee), thanks!
Comment 2 Robert Wilkens 2012-06-18 17:02:39 UTC
I'm marking this as resolved/fixed, as the person who reported it.