Why can't I catch a luabind::error exception when my lua code throws an error?

Question

When you call a LUA function from c++ and there is a runtime error LuaBind throws a luabind::error exception that you can catch and then read the stack to see what the error was. My debugger definitely catches this exception but when I let the debugger continue, instead of the exception being caught in my code the program immediately terminates.

The exception is thrown in "call_member.hpp" in the LuaBind include files from the destructor ~proxy_member_void_caller().

The problem occurs with simple test code. I am using Xcode 5 with LuaBind 0.9.1.

score 9 · Accepted Answer · edited May 23 '17 at 11:58

9

It turns out that it is bad practice to throw exceptions in destructors. With C++11 destructors are implicitly noexcept(true), so if an exception occurs the program terminates. LuaBind uses exceptions in destructors, so on my modern compiler the program terminated. Editing the method signature to:

~proxy_member_void_caller() noexcept(false) {}

allows you to catch exceptions from LuaBind in c++11.

edited May 23 '17 at 11:58

Community

1
1

answered May 09 '14 at 21:33

Sean Dawson

5,587
2
27
34

2

It's a little more than bad practice! – Lightness Races in Orbit May 09 '14 at 21:47
Who throws in destructors, honestly! – W.B. May 09 '14 at 22:09
1

In addition to ~proxy_member_void_caller() you also need to patch ~proxy_member_caller() in the same file. In addition you probably want to get the similar ones in call_function.hpp too – radman Mar 01 '18 at 15:06

Why can't I catch a luabind::error exception when my lua code throws an error?

1 Answers1

Linked

Related