[Mono-dev] Regression with Linux update

[the mad mole]

I have been happily running mono 2.11.1 cross-compiled for MIPS with gcc
4.5.3-1.2.  Out of nearly 500 runtime tests, only
async-exc-compilation.exe  and monitor.exe were failing (hangs).  Recenly
our SOC vendor upgraded us from 2.6.37-2.2 to -2.8, which has caused a
significant regression in functionality: 117 of the runtime tests now
fail.  It appears the culprit in many of the failures is the use of
try-catch.  The following simple program demonstrates the problem:

using System;
namespace trycatch
{
    class MainClass
    {
        public static void Main (string[] args)
        {
            int[] array = new int[5] {10, 20, 30, 40, 50};
            try {
                Console.WriteLine("Entering first try clause:");
            } catch {
                Console.WriteLine("Entering first catch clause");
            }
            try {
                Console.WriteLine("Entering second try clause:
array[5]={0}", array[5]);
            } catch {
                Console.WriteLine("Entering second catch clause");
            }
        }
    }
}
Before, the expected behavior was seen:

# mono trycatch.exe
Entering first try clause:
Entering second catch clause
Now, raising the exception in the second try-catch block aborts the program:

# mono trycatch.exe
Entering first try clause:
Stacktrace:

Aborted
Has anyone seen behavior like this?  Any ideas where to start looking?

TMM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20120515/c7eac1bd/attachment.html>