Bug 39937 - csharp repl uncaught IndexOutOfRange exception
Summary: csharp repl uncaught IndexOutOfRange exception
Alias: None
Product: Tools
Classification: Mono
Component: csharp ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-03-28 04:05 UTC by owenlharvey
Modified: 2017-10-27 10:50 UTC (History)
3 users (show)

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

Exception stack trace (2.55 KB, text/plain)
2016-03-28 04:05 UTC, owenlharvey

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 owenlharvey 2016-03-28 04:05:38 UTC
Created attachment 15532 [details]
Exception stack trace

In the csharp repl for mono there is an uncaught indexoutofrange exception when using new code completion system.

To replicate this bug, open the repl and type "Int32.", then scroll down to "TryParse", back up to "ToString", and then down to "TryParse" again. The second time you select TryParse, the exception will be thrown, crashing the session.

The same issue occurs with "Int64" and "Double", where you scroll to the end of the completion list, up one entry, and then back down.

I have attached a dump of the exception message.
Comment 1 Marek Safar 2017-10-27 10:50:21 UTC
I cannot reproduce the issue with recent Mono version (5.8)