EXC_BAD_ACCESS when using std::function w/ std::bind
Asked Answered
F

1

3

After upgrading to XCode 5 using std::function with std::bind appears to be generating EXC_BAD_ACCESS exceptions. It looks as if the __base pointer inside the implementation of std::function ends up being null, resulting in the bad access, but I'm not clear on why that would be the case. Does anyone have an insight into either what I'm doing wrong?

Here is sample code that illustrates the problem.

struct A
{
    void foo(bool b)
    {
        std::cout << b << std::endl;
    }

    void go()
    {
        // ok
        auto a = std::bind(&A::foo, this, std::placeholders::_1);
        a(true);

        // ok
        std::function<void(A*, bool)> b = std::bind(&A::foo, std::placeholders::_1, std::placeholders::_2);
        b(this, true);

        // ok
        std::function<void(A*, bool)> c = std::bind(&A::foo, this, std::placeholders::_2);
    c(this, true);

        // EXC_BAD_ACCESS
        std::function<void(bool)> f = std::bind(&A::foo, this, std::placeholders::_1);
        f(true);
    }
};
...
...

A a;
a.go();
Freesia answered 6/11, 2013 at 18:40 Comment(1)
Cannot reproduce with neither gcc 4.7.2 nor clang 3.2 (Linux)Draw
N
0

It seems that this may be a bug that has been fixed. I had a similar issue (std::bind to a std::function crashes with Clang) where the solution simply was to upgrade from XCode 5.0.1 to XCode 5.0.2.

I tried your code and it seems to work fine with XCode 5.0.2 (have not tried with 5.0.1).

Neveda answered 20/11, 2013 at 14:46 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.