https://bugs.winehq.org/show_bug.cgi?id=44589
Bug ID: 44589 Summary: The finally{} of a try/catch/finally on MS .NET doesn't appear to be be respected as it should Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: epigramx@yahoo.com Distribution: ---
My own code on MS seems to adhere to the notion that if something is in a finally {} of a try/catch/finally it must always be called unless the program doesn't continue at all.
On wine though (tested on current -devel and .NET 4.5.2) that doesn't seem to be the case. Calls inside the finally{} may be ignored or in general be inconsistent.
https://bugs.winehq.org/show_bug.cgi?id=44589
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 CC| |focht@gmx.net Status|UNCONFIRMED |NEEDINFO
--- Comment #1 from Anastasius Focht focht@gmx.net --- Hello,
please specify the exact Wine version you tested with.
--- quote --- Calls inside the finally{} may be ignored or in general be inconsistent. --- quote ---
You have to be more specific on what *exactly* doesn't work.
Attach some small app (test-case), demonstrating what you think is incorrect behaviour.
* C# source of .NET console test app (with output in try/catch/finally that shows the code paths taken) * IL executable of that test app, if it's your own (to avoid installing .NET SDK).
Regards
https://bugs.winehq.org/show_bug.cgi?id=44589
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org