search for: set_new_handl

Displaying 6 results from an estimated 6 matches for "set_new_handl".

Did you mean: set_new_handler
2008 Aug 04
1
[LLVMdev] llvm-c bindings and exceptions?
...isn't needed. It does use 'new' (e.g. LLVMCreateModuleProviderForExistingModule), and also calls C++ functions which in turn use new (e.g. LLVMGetBitcodeModuleProvider -> llvm::getBitcodeModuleProvider), so std::bad_alloc is a possibility (a quick search didn't turn up any "set_new_handler" also). There might also be C++ client code (e.g. overridden virtual functions in custom passes) which might (unintentionally) throw exceptions. Regards, -Mahadevan.
2014 Feb 10
6
[LLVMdev] [RFC] Simple control-flow integrity
...xternal functions can return pointers to external functions that were not exposed at LTO time. The canonical example in this class is dlsym, which is used extensively by many projects. Other commonly used cases are signal/sigaction (returns the old signal handler), XSetErrorHandler from X, and std::set_new_handler from the Standard C++ library. But this happens with any dynamically-linked library that has a method that returns function pointers. - Internal code that takes function pointer arguments can be passed to external code and have external function pointers passed to it as arguments. This patte...
2008 Aug 03
2
[LLVMdev] llvm-c bindings and exceptions?
Hi, Just wondering -- shouldn't all (C linkage) functions exposed by LLVM-C (and written in C++) be catching std::exception (or "...") to prevent exceptions being passed on to C callers? [OT: Does clang warn about throw statements from within "extern C" functions?] Thanks & Regards, -Mahadevan.
2008 Aug 03
0
[LLVMdev] llvm-c bindings and exceptions?
On Aug 3, 2008, at 7:54 AM, Mahadevan R wrote: > Hi, > > Just wondering -- shouldn't all (C linkage) functions exposed by > LLVM-C (and written in C++) be catching std::exception (or "...") to > prevent exceptions being passed on to C callers? LLVM doesn't use exceptions in anything that has C bindings, so the catch isn't needed. > [OT: Does clang warn
2011 Sep 23
0
Wine release 1.3.29
...Added basic_string::find(basic_string, size_t) implementation. msvcp90: Added basic_string::operator=(char) implementation. msvcp90: Added basic_string::push_back(char) implementation. msvcp: Sync spec files. msvcrt: Improve operator new implementation. msvcp90: Added set_new_handler implementation. msvcp90: Added basic_string::empty() implementation. msvcp90: Added basic_string::{begin,rbegin,end,rend} implementation. msvcp90: Added basic_string::_Chassign implementation. msvcp90: Added basic_string::_Copy_s implementation. msvcp90: Added basic_...
2008 Dec 20
0
Wine release 1.1.11
...static. msvcrt/tests: Make void test_cp_table() static. ntdll/tests: Make rtlraiseexception_vectored_handler() static. shell32/tests: Make test_cbsize() static. ole32/tests: Make test_runnable() static. user32/tests: Make some functions static. msvcrt: Point the set_new_handler() entrypoint to the right implementation. wineoss.drv: Make widOpen() and wodOpen() static. userenv/tests: Make userenv_dbgstr_w() static. kernel32: Remove _hread16() as it is not used. Move _hwrite16() next to the other related functions. wininet & winhttp: Remove the...