labath added a comment. In https://reviews.llvm.org/D33035#798857, @abhishek.aggarwal wrote:
> Hi Pavel .. I could remove all exception handling code from source files. > However, I am still wondering how to disable exception handling while > providing python functions for C++ APIs of the features. Can you suggest > something here? The whole problem is occurring because of the use of vector<> > as an argument to one of the C++ APIs. To provide a python interface for > these APIs, I am forced to include std_vector.i (please see > tools/intel-features/intel-pt/interface/PTDecoder.i file) which is > introducing exception handling code. Hm... that's a bit of a drag. I guess the SB API never ran into this problem because it always provides it's own vector-like classes (SBModuleList, SBFileSpecList, etc.). I guess the most canonical way would be to follow that example and have your own class for a list of instructions. However, that is a bit annoying, so I do see a case for making code generated by swig as an exception to the rule. https://reviews.llvm.org/D33035 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
