Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 81 [details]
example app to demo this issue.
I have a linq query that I have performed. I have forced it to go ahead and execute via calling .ToList<....>(). I have gone into the locals/watch window. I have tried to drill down to the items into the list, and have received a message telling me that the item I am trying to look at have already been garbaged collected. the objects are still around. I am guessing that the debugger doesn't know that the query has actually been run, but that it is a personal opinion based on nothing more than a first guess.
I am running:
mac OSX 10.6.8
The error occurs in the simulator. I suspect it would occur if debugging on the device, but I am unable to verify that at this time.
Created attachment 82 [details]
Screenshot of issue
It seems that _data is also a list full of GC'd items.
Btw, do you have a search string you typically use? I had to try a bunch of strings before I finally got one that got any results in 'test' (most of the time the test list would result in an empty list)
have done a bit of digging and it seems that either MD is sending the debugger the wrong object id or else the debugger's get_object[_allow_null]() is broken somehow.
it's gotta be something wrong with the way MD requests array info from sdb or a bug in the way sdb responds
I can't reproduce this anymore in MonoDevelop 2.8.4, so I guess it's been fixed?
Wally, can you confirm?