What causes std::bad_function_call?

25,142

Solution 1

Sure- the easiest is where you try to call a std::function that's empty.

int main() {
    std::function<int()> intfunc;
    int x = intfunc(); // BAD
}

Solution 2

In my case, the problem was in the capture list. I have a recursive lambda function.

//decl
std::function<void(const SBone*, const core::vector3df&, const core::quaternion&)> f_build;
f_build = [&f_build](const SBone* bone, const core::vector3df& pos, const core::quaternion& rot)
{
...
}

Missing & from f_build in the capture list generates a bad call.

Solution 3

"Performing a function call without having a target to call throws an exception of type std::bad_function_call"

    std::function<void(int,int)> f;
    f(33,66); // throws std::bad_function_call

No credits to me....its Nicolai Josuttis Pundit of C++ Standard Lib

Solution 4

Call of a temporary function also can throw:

struct F
{
    const std::function<void()>& myF;

    F(const std::function<void()>& f) : myF(f) {}

    void call()
    {
        myF();
    }
};

int main()
{
    F f([]{ std::cout << "Hello World!" << std::endl;});

    f.call();

    return 0;
}

But this depend on compiler (vc++ throws, g++ not).

Share:
25,142
Ken Bloom
Author by

Ken Bloom

Updated on July 09, 2022

Comments

  • Ken Bloom
    Ken Bloom almost 2 years

    I've seen a few questions that refer to the std::bad_function_call exception, but haven't been able to find out any by Googling about what causes this exception.

    What kind of behavior is supposed to cause this exception? Can you give me minimal examples that don't have other semantic problems also going on?