Search

/Ehsc & /Eha & stack unwinding by Tomas Potrusil

Closed
as Fixed Help for as Fixed

2
0
Sign in
 to vote
Type: Bug
ID: 382860
Opened: 11/19/2008 3:35:26 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I have two libraries: A and B. A is C++ library compiled with /Ehsc compiler switch, B is C++/CLI library (compiled with /Eha). When an exception is thrown in A and caught in B then the stack is not unwinded.
Details (expand)
Product Language
English

Version

Visual Studio 2008 SP1
Operating System
Windows XP Professional
Operating System Language
English
Steps to Reproduce
1. Create native static C++ library (/Ehsc) that throws an exception. Store an object (obj) on stack before the exception is thrown.
2. Create managed (C++/CLI) application that catches that exception.
Actual Results
The exception is caught but the destructor of the obj object is not called.
Expected Results
The exception is caught and the destructor of the obj object is called.
TAP Code (if applicable)
 
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

Sign in to post a comment.
Posted by Dmitriy Ovdienko on 7/16/2009 at 10:56 PM
Could you please provide us with hotfix?
Posted by Microsoft on 1/12/2009 at 11:51 AM
Thanks for reporting this issue. We have identified the root cause and fixed this issue for the next release of CLR.
Posted by Microsoft on 11/25/2008 at 2:20 AM
Thanks for your feedback

We were able to reproduce the issue you are seeing. We are escalating this issue to the product unit who works on that specific feature area. The product team will review this issue and make a decision on whether they will fix it or not for the next release
Posted by Tomas Potrusil on 11/24/2008 at 11:36 PM
I attached the project you requested. There is one native function that optionally throws an exception. When it is called from managed code and the exception is thrown there the stack of the function is not unwinded.
Posted by Microsoft on 11/24/2008 at 5:53 PM
Thanks for reporting the issue.

In order to fix the issue, we must first reproduce the issue in our labs exactly like what you saw. We are unable to reproduce the issue with the steps you provided. We need to know more details about how you throw the exception so that we can make a decision it is by design or a bug.

Could you please provide us with a zipped project file?

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thanks again for your efforts and we look forward to hearing from you.
Visual Studio Product Team
Posted by Microsoft on 11/20/2008 at 6:24 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com/)
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement