[Mono.Debugger.Soft] Prettified PrimitivateValue ToString for null values
Reset the async state and frame info for still running threads when resuming the vm in sdb. Fixes #4737.
Fix DataContractSerializer with duplicate qname

- Fix bug 4794 by searching the SerializationMap with both type and
  qname in all but several cases (see bug report comments)

- Add separate list for known types to mimic behavior of the .NET
  runtime

- Make previous test fixtures public so that the unit tests will be run

- Remove unused private method

- Add unit test for bug 4794
Fix parsing of -w argument. Fixes #4853
Merge branch 'master' of github.com:mono/mono
Fix XmlTextWriter's use of NewLineHandling.

- Move the setting of newline_handling early enough that Initialize()
  can see it.
- Reduce the set of characters that trigger the slow path for
  attribute values for the NewLineHandling.None case.
- Rewrite the handling of \t, \r and \n to match the MS docs
  (which match the observed behavior of their implementation)
- Add some tests.
More fixes for passing/receiving nullables in sdb. Fixes #4659.
This is the addition of a quick and dirty NUnit test for Bug 4786

This bug was fixed in another commit/push by Robert Wilkens (me).
This NUnit test will fail without the patch (It will raise a
NullReferenceException from within mono), but with the patch for that
bug it will not raise an exception and the test will exit cleanly.

Please note, the top of this patch source sets up a temporary network
socket to listen to a port which pool.GetConnection() simply tries to connect
to.  No data is transfered so nothing needed to be done other than to
call Listen() on that socket which was bound to the port.  If the listen fails,
it means something else is listening already, which is fine, so we ignore
any excpetions from this part of the code (catch and ignore).
This is a minor change to earlier commit which removes a commented out
sql server that should not have been there.  It changes nothing functionally,
but the server is a temporary server, so referencing it didn't make sense.
Force disposal of Sqlite commands with using-statements in order to better isolate the unit tests.
Merge pull request #288 from ewxrjk/xmlwriter

Fix XmlTextWriter's use of NewLineHandling.
Merge pull request #286 from dafergu2/bug4794

Fix DataContractSerializer with duplicate qname
[Mono.Debugger.Soft] Don't make Connection disposable.
Add exception handlers to MethodBodyMirror
Merge pull request #290 from jbevain-forks/methodbodymirror-exceptions

Add exception handlers to MethodBodyMirror
Add a missing $(srcdir) to bug-3903 build command. Patch by KISHIMOTO, Makoto.
Raise an exception instead of aborting if a pinvoke method is not found in full-aot mode.
Fiz a domain unload race regarding finalizable objects.

	* sgen-gc.c (mono_gc_clear_domain): It's possible to have a finalizable object
	survive mono_domain_finalize and leak into mono_domain_free, so we make sure this
	won't crash by removing from the fin hashtable all objects that belong to the
	doomed domain.
When cleaning up the finalizers of a domain, do it in a way that reduces the chance of leftover objects.

	* gc.c (finalize_domain_objects): When cleaning up a domain, we run two kinds of finalizers,
	those that have already been queued and those for objects that remain alive.

	A common problem we need to deal is that some finalizers allocate other finalizable objects
	when doing seeminly trivial operations such as String.IndexOf - which might require the Thread
	object of the finalizer thread to be instantiated.

	We handle those new objects by draining the registered finalizers set until none shows up. This fails
	if we run the queued finalizers after that.

	The order onto which finalizers are run on domain unload is unspecified and the new behavior can
	be argued to be more natural.
[Mono.Debugger.Soft] Fixed building of tests