Bug 24630 - Crash of Insight inside Forms
Summary: Crash of Insight inside Forms
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-11-18 18:11 UTC by Ian
Modified: 2015-02-13 06:51 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 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 Ian 2014-11-18 18:11:10 UTC
Using the newest Beta bits.

VS 2013, iPhone 5s

I have a really simple page:

        public AccountsPage()
        {
            Title = "Accounts";
            Icon = "account.png";

            
            BindingContext = new AccountsViewModel();

            toolbarItem = new ToolbarItem("?", "accounts.png",async  () =>
            {
                await DisplayAlert("Hi", "Clicked me",null);
            }, 0, 0);

Adding the toolbar code causes the pageto explode when the toolbar button is pressed



---------------------------

---------------------------
Exception in OnUnhandledException:

Mono.Debugger.Soft.AbsentInformationException: Debug information is not available for this frame.

   at Mono.Debugger.Soft.VirtualMachine.ErrorHandler(Object sender, ErrorHandlerEventArgs args)

   at Mono.Debugger.Soft.Connection.SendReceive(CommandSet command_set, Int32 command, PacketWriter packet)

   at Mono.Debugger.Soft.Connection.StackFrame_GetThis(Int64 thread_id, Int64 id)

   at Mono.Debugger.Soft.StackFrame.GetThis()

   at Mono.Debugging.Soft.ThisValueReference.get_Value()

   at Mono.Debugging.Soft.SoftDebuggerAdaptor.GetHoistedLocalVariables(SoftEvaluationContext cx, ValueReference vthis)

   at Mono.Debugging.Soft.SoftDebuggerAdaptor.OnGetLocalVariables(EvaluationContext ctx)

   at Mono.Debugging.Evaluation.ExpressionEvaluator.GetLocalVariables(EvaluationContext ctx)

   at Mono.Debugging.Evaluation.BaseBacktrace.GetFrameInfo(Int32 frameIndex, EvaluationOptions options, Boolean ignoreEvalStatus)

   at Mono.Debugging.Evaluation.BaseBacktrace.GetException(Int32 frameIndex, EvaluationOptions options)

   at Xamarin.VisualStudio.Debugger.MonoToolsDebuggerSession.OnUnhandledException(Object sender, TargetEventArgs args)
---------------------------
OK   
---------------------------
Comment 1 Jason Smith [MSFT] 2015-02-13 06:51:12 UTC
You may not pass null to the Cancel argument. You will now get an ArgumentNullException