try-catch-finally

Can anyone explain why this finally block is not executed? I have read posts about when to expect finally block not be executed, but this seems to be another case. This code needs TopShelf and log4net. I am running .net 4.5 I guess it must be the Windows Service engine that kicks in on unhandled exceptions, but why is it running before the finally block has finished? using log4net; using log4net.Config; using System; using System.Threading; using Topshelf; namespace ConsoleApplication1 { public class HostMain { static void Main(string[] args) { HostFactory.Run(x => { x.Service<HostMain>(s => {

Hey all. I've been reading up on Apple's suggestions for when/where/how to use NSError versus @try/@catch/@finally. Essentially, my impression is that Apple thinks it best to avoid the use of exception handling language constructs except as a mechanism for halting program execution in unexpected error situations (maybe someone could give an example of such a situation?) I come from Java, where exceptions are the way to go when one wants to handle errors. Admittedly, I'm still in the Java thoughtspace, but I'm slowly coming to grips with all that NSError has to offer. One thing I'm hung up on

When compiling the following code with a simple try/finally block, the Java Compiler produces the output below (viewed in the ASM Bytecode Viewer): Code: try { System.out.println("Attempting to divide by zero..."); System.out.println(1 / 0); } finally { System.out.println("Finally..."); } Bytecode: TRYCATCHBLOCK L0 L1 L1 L0 LINENUMBER 10 L0 GETSTATIC java/lang/System.out : Ljava/io/PrintStream; LDC "Attempting to divide by zero..." INVOKEVIRTUAL java/io/PrintStream.println (Ljava/lang/String;)V L2 LINENUMBER 11 L2 GETSTATIC java/lang/System.out : Ljava/io/PrintStream; ICONST_1 ICONST_0 IDIV

My understanding is that finally clauses must *always* be executed if the try has been entered. import random from multiprocessing import Pool from time import sleep def Process(x): try: print x sleep(random.random()) raise Exception('Exception: ' + x) finally: print 'Finally: ' + x Pool(3).map(Process, ['1','2','3']) Expected output is that for each of x which is printed on its own by line 8, there must be an occurrence of 'Finally x'. Example output: $ python bug.py 1 2 3 Finally: 2 Traceback (most recent call last): File "bug.py", line 14, in <module> Pool(3).map(Process, ['1','2','3'])

Considering this code, can I be absolutely sure that the finally block always executes, no matter what something() is? try { something(); return success; } catch (Exception e) { return failure; } finally { System.out.println("I don't know if this will get printed out"); } jodonnell Yes, finally will be called after the execution of the try or catch code blocks. The only times finally won't be called are: If you invoke System.exit() If the JVM crashes first If the JVM reaches an infinite loop (or some other non-interruptable, non-terminating statement) in the try or catch block If the OS

This question already has an answer here: Does a finally block always get executed in Java? 47 answers Given the following try/catch block in java: try{ return; } catch(SomeException e){ System.out.println(e); } finally{ System.out.println("This is the finally block"); } and according to this post: " Does finally always execute in Java? " I can see that the program's output will be 'This is the finally block'. However, I can't figure out how that would be possible since the print statement is preceded by a return... I suspect that this behaviour has something to do with threading, however I am

This question already has an answer here: When finally is executed? [duplicate] 10 answers finally always gets executed last, so the statement x = 3 should be executed last. But, when running this code, the value returned is 2. Why? class Test { public static void main (String[] args) { System.out.println(fina()); } public static int fina() { int x = 0; try { x = 1; int a = 10/0; } catch (Exception e) { x = 2; return x; } finally { x = 3; } return x; } } That's because the finally block is executed after the catch clause. Inside your catch you return x , and at that point its value is 2, which