Bug 19136 - ThreadAbortException Not finishing Finally block ARM
Summary: ThreadAbortException Not finishing Finally block ARM
Status: NEW
Alias: None
Product: Runtime
Classification: Mono
Component: JIT (show other bugs)
Version: 3.2.x
Hardware: Other Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-04-17 15:28 UTC by nicholas.rudh
Modified: 2014-06-21 09:55 UTC (History)
4 users (show)

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


Description nicholas.rudh 2014-04-17 15:28:58 UTC
	When running the mono unit tests on my ARM running Linux I get an error when executing block_guard_restore_aligment_on_exit.exe. When I debug the program using Xamarin Studio remote debugging I found that once Thread.Abort is called the Finally block does not finish, instead just throws the exception.

Steps to Reproduce: 
1)	Execute block_guard_restore_aligment_on_exit.exe from the mono unit tests in directory $Top_Dir/mono/tests/

Actual Results: 
	Exception is thrown from the finally block

Expected Results: 
	Finish finally block and because of the Thread.ResetAbort not throw an exception.

Build Date & Platform: platform:
 ARM running PetaLinux v2013.10 (yocto 1.4) 
 Mono version 3.2.8

It seems like this problem was found in Bug #16808, and this test does work on my Ubuntu machine. This makes me think it could be ARM specific, so any help would be great. If you need any more information I can provide it.
Comment 1 Zoltan Varga 2014-04-18 05:30:19 UTC
The relevant functionality is not yet implemented on arm.
Comment 2 nicholas.rudh 2014-04-18 15:30:52 UTC
Thanks for the quick response. Is there an ETA on when this could be implemented, or is there not enogh demand for the fix?
Comment 3 Damien Diederen 2014-06-21 09:55:57 UTC
For the benefit of people googling failing test names:

  finally_block_ending_in_dead_bb.cs => finally_block_ending_in_dead_bb.exe

currently fails for (what seems to be) the same reason, as explained
by Rodrigo Kumpera in:


Note You need to log in before you can comment on or make changes to this bug.