草庐IT

c++ - Boost.Coroutine 在 iPhone 上崩溃

coder 2024-01-25 原文

是否有人试图在 iOS 应用程序中使用 Boost.Coroutine 库？ 如果是，是否有效？

我现在正在尝试这样做，但是当尝试展开堆栈应用程序的不完整协程以未捕获的异常 forced_unwind() 终止时。

我已经在其他平台(i386(ios 模拟器)和 elf armv7(htc one x，one v))上运行了这个库，并且运行良好。但是 iOS.. :[

附加信息:

我正在尝试运行来自 boost/coroutine/example 的 unwind.cpp 示例: https://github.com/olk/boost-coroutine/blob/master/example/cpp03/unwind.cpp

堆栈是:

libc++abi.dylib: terminating with uncaught exception of type yboost::coroutines::detail::forced_unwind
(lldb) bt
* thread #1: tid = 0x258dd, 0x399eb1fc libsystem_kernel.dylib`__pthread_kill + 8, queue = 'com.apple.main-thread, stop reason = signal SIGABRT
    frame #0: 0x399eb1fc libsystem_kernel.dylib`__pthread_kill + 8
    frame #1: 0x39a52a52 libsystem_pthread.dylib`pthread_kill + 58
    frame #2: 0x3999c02c libsystem_c.dylib`abort + 76
    frame #3: 0x38dea98e libc++abi.dylib`abort_message + 74
    frame #4: 0x38e036e6 libc++abi.dylib`default_terminate_handler() + 254
    frame #5: 0x3943b95c libobjc.A.dylib`_objc_terminate() + 228
    frame #6: 0x38e011b2 libc++abi.dylib`std::__terminate(void (*)()) + 78
    frame #7: 0x38e012b0 libc++abi.dylib`std::terminate() + 156
    frame #8: 0x000ab2fc CoroutinesTest`__clang_call_terminate + 16
    frame #9: 0x000aefaa CoroutinesTest`yboost::coroutines::detail::pull_coroutine_object<void, void (this=0x15645b90)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> >::unwind_stack_() + 358 at pull_coroutine_object.hpp:804
    frame #10: 0x000aee02 CoroutinesTest`yboost::coroutines::detail::pull_coroutine_object<void, void (this=0x15645b90)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> >::~pull_coroutine_object() + 62 at pull_coroutine_object.hpp:862
    frame #11: 0x000aed9e CoroutinesTest`yboost::coroutines::detail::pull_coroutine_object<void, void (this=0x15645b90)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> >::~pull_coroutine_object() + 14 at pull_coroutine_object.hpp:860
    frame #12: 0x000aefea CoroutinesTest`yboost::coroutines::detail::pull_coroutine_object<void, void (&)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> >::destroy_(std::__1::allocator<yboost::coroutines::detail::pull_coroutine_object<void, void (&)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> > >&, yboost::coroutines::detail::pull_coroutine_object<void, void (&)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> >*) [inlined] std::__1::allocator<yboost::coroutines::detail::pull_coroutine_object<void, void (this=0x15645cbc, __p=0x15645b90)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> > >::destroy(yboost::coroutines::detail::pull_coroutine_object<void, void (&)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> >*) + 34 at memory:1739
    frame #13: 0x000aefe0 CoroutinesTest`yboost::coroutines::detail::pull_coroutine_object<void, void (alloc=0x15645cbc, p=0x15645b90)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> >::destroy_(std::__1::allocator<yboost::coroutines::detail::pull_coroutine_object<void, void (&)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> > >&, yboost::coroutines::detail::pull_coroutine_object<void, void (&)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> >*) + 24 at pull_coroutine_object.hpp:783
    frame #14: 0x000aed8c CoroutinesTest`yboost::coroutines::detail::pull_coroutine_object<void, void (this=0x15645b90)(yboost::coroutines::push_coroutine<void>&), yboost::coroutines::detail::standard_stack_allocator, std::__1::allocator<yboost::coroutines::pull_coroutine<void> >, yboost::coroutines::push_coroutine<void> >::deallocate_object() + 24 at pull_coroutine_object.hpp:892
    frame #15: 0x000ad9a4 CoroutinesTest`yboost::coroutines::detail::intrusive_ptr_release(p=0x15645b90) + 116 at pull_coroutine_base.hpp:311
    frame #16: 0x000ad92a CoroutinesTest`yboost::intrusive_ptr<yboost::coroutines::detail::pull_coroutine_base<void> >::~intrusive_ptr(this=0x27d5d990) + 34 at intrusive_ptr.hpp:97
    frame #17: 0x000ad902 CoroutinesTest`yboost::intrusive_ptr<yboost::coroutines::detail::pull_coroutine_base<void> >::~intrusive_ptr(this=0x27d5d990) + 14 at intrusive_ptr.hpp:96
    frame #18: 0x000ad8e8 CoroutinesTest`yboost::coroutines::pull_coroutine<void>::~pull_coroutine(this=0x27d5d990) + 16 at coroutine.hpp:1784
    frame #19: 0x000ad8d2 CoroutinesTest`yboost::coroutines::pull_coroutine<void>::~pull_coroutine(this=0x27d5d990) + 14 at coroutine.hpp:1784
    frame #20: 0x000aa0a0 CoroutinesTest`(anonymous namespace)::runnable() + 260 at CoroRunner.cpp:38
    frame #21: 0x000a9f98 CoroutinesTest`CoroRunner::run(this=0x15641dd0) + 12 at CoroRunner.cpp:84
    frame #22: 0x000c723e CoroutinesTest`-[Runner run](self=0x1563f900, _cmd=0x31edde22) + 34 at Runner.mm:32
    frame #23: 0x000c65ba CoroutinesTest`-[TPCAppDelegate application:didFinishLaunchingWithOptions:](self=0x15539dc0, _cmd=0x31eae996, application=0x15532840, launchOptions=0x00000000) + 666 at TPCAppDelegate.m:21
    frame #24: 0x31937424 UIKit`-[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 276
    frame #25: 0x31936e6a UIKit`-[UIApplication _callInitializationDelegatesForURL:payload:suspended:] + 1390
    frame #26: 0x319314b8 UIKit`-[UIApplication _runWithURL:payload:launchOrientation:statusBarStyle:statusBarHidden:] + 720
    frame #27: 0x318cbbe6 UIKit`-[UIApplication handleEvent:withNewEvent:] + 3142
    frame #28: 0x318caedc UIKit`-[UIApplication sendEvent:] + 72
    frame #29: 0x31930ca0 UIKit`_UIApplicationHandleEvent + 664
    frame #30: 0x33dac76c GraphicsServices`_PurpleEventCallback + 608
    frame #31: 0x33dac356 GraphicsServices`PurpleEventCallback + 34
    frame #32: 0x2f10b77e CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 34
    frame #33: 0x2f10b71a CoreFoundation`__CFRunLoopDoSource1 + 346
    frame #34: 0x2f109ee6 CoreFoundation`__CFRunLoopRun + 1406
    frame #35: 0x2f074540 CoreFoundation`CFRunLoopRunSpecific + 524
    frame #36: 0x2f074322 CoreFoundation`CFRunLoopRunInMode + 106
    frame #37: 0x3192ff42 UIKit`-[UIApplication _run] + 762
    frame #38: 0x3192b1e4 UIKit`UIApplicationMain + 1136
    frame #39: 0x000c67c4 CoroutinesTest`main(argc=1, argv=0x27d5fcf4) + 116 at main.m:16

最佳答案

ARM 上的 IOS 使用与 AAPCS(标准)不同的 ABI。 boost.coroutine 在内部使用 boost.context 进行上下文切换/跳转。 直到 boost-1.55 bost.context 不支持 IOS 的 ABI。

关于c++ - Boost.Coroutine 在 iPhone 上崩溃，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/19726132/

ampCoroutinecoroutinesyboostc++iosiphoneexceptionboost

有关c++ - Boost.Coroutine 在 iPhone 上崩溃的更多相关文章

  1. ruby - 检查 "command"的输出应该包含 NilClass 的意外崩溃 - 2

    为了将Cucumber用于命令行脚本，我按照提供的说明安装了arubagem。它在我的Gemfile中，我可以验证是否安装了正确的版本并且我已经包含了require'aruba/cucumber'在'features/env.rb'中为了确保它能正常工作，我写了以下场景:@announceScenario:Testingcucumber/arubaGivenablankslateThentheoutputfrom"ls-la"shouldcontain"drw"假设事情应该失败。它确实失败了，但失败的原因是错误的:@announceScenario:Testingcucumber/ar

  2. ruby-on-rails - 如何优雅地重启 thin + nginx？ - 2

    我的瘦服务器配置了nginx，我的ROR应用程序正在它们上运行。在我发布代码更新时运行thinrestart会给我的应用程序带来一些停机时间。我试图弄清楚如何优雅地重启正在运行的Thin实例，但找不到好的解决方案。有没有人能做到这一点？ 最佳答案 #Restartjustthethinserverdescribedbythatconfigsudothin-C/etc/thin/mysite.ymlrestartNginx将继续运行并代理请求。如果您将Nginx设置为使用多个上游服务器，例如server{listen80;server

  3. Ruby Readline 在向上箭头上使控制台崩溃 - 2

    当我在Rails控制台中按向上或向左箭头时，出现此错误:irb(main):001:0>/Users/me/.rvm/gems/ruby-2.0.0-p247/gems/rb-readline-0.4.2/lib/rbreadline.rb:4269:in`blockin_rl_dispatch_subseq':invalidbytesequenceinUTF-8(ArgumentError)我使用rvm来管理我的ruby​​安装。我正在使用=>ruby-2.0.0-p247[x86_64]我使用bundle来管理我的gem，并且我有rb-readline(0.4.2)(人们推荐的最少

  4. ruby - 使用 `+=` 和 `send` 方法 - 2

    如何将send与+=一起使用？a=20;a.send"+=",10undefinedmethod`+='for20:Fixnuma=20;a+=10=>30 最佳答案 恐怕你不能。+=不是方法，而是语法糖。参见http://www.ruby-doc.org/docs/ProgrammingRuby/html/tut_expressions.html它说Incommonwithmanyotherlanguages,Rubyhasasyntacticshortcut:a=a+2maybewrittenasa+=2.你能做的最好的事情是:

  5. ruby - 如何计算 Liquid 中的变量 +1 - 2

    我对如何计算通过{%assignvar=0%}赋值的变量加一完全感到困惑。这应该是最简单的任务。到目前为止，这是我尝试过的:{%assignamount=0%}{%forvariantinproduct.variants%}{%assignamount=amount+1%}{%endfor%}Amount:{{amount}}结果总是0。也许我忽略了一些明显的东西。也许有更好的方法。我想要存档的只是获取运行的迭代次数。 最佳答案 因为{{incrementamount}}将输出您的变量值并且不会影响{%assign%}定义的变量，我

  6. arrays - Ruby 数组 += vs 推送 - 2

    我有一个数组数组，想将元素附加到子数组。+=做我想做的，但我想了解为什么push不做。我期望的行为(并与+=一起工作):b=Array.new(3,[])b[0]+=["apple"]b[1]+=["orange"]b[2]+=["frog"]b=>[["苹果"],["橙子"],["Frog"]]通过推送，我将推送的元素附加到每个子数组(为什么？):a=Array.new(3,[])a[0].push("apple")a[1].push("orange")a[2].push("frog")a=>[[“苹果”、“橙子”、“Frog”]、[“苹果”、“橙子”、“Frog”]、[“苹果”、“

  7. += 的 Ruby 方法 - 2

    有没有办法让Ruby能够做这样的事情？classPlane@moved=0@x=0defx+=(v)#thisiserror@x+=v@moved+=1enddefto_s"moved#{@moved}times,currentxis#{@x}"endendplane=Plane.newplane.x+=5plane.x+=10putsplane.to_s#moved2times,currentxis15 最佳答案 您不能在Ruby中覆盖复合赋值运算符。任务在内部处理。您应该覆盖+，而不是+=。plane.a+=b与plane.a=

  8. ruby - Sinatra + Heroku + Datamapper 使用 dm-sqlite-adapter 部署问题 - 2

    出于某种原因，heroku尝试要求dm-sqlite-adapter，即使它应该在这里使用Postgres。请注意，这发生在我打开任何URL时-而不是在gitpush本身期间。我构建了一个默认的Facebook应用程序。gem文件:source:gemcuttergem"foreman"gem"sinatra"gem"mogli"gem"json"gem"httparty"gem"thin"gem"data_mapper"gem"heroku"group:productiondogem"pg"gem"dm-postgres-adapter"endgroup:development,:t

  9. ruby - Ruby 中字符串运算符 + 和 << 的区别 - 2

    我是Ruby和这个网站的新手。下面两个函数是不同的，一个在函数外修改变量，一个不修改。defm1(x)x我想确保我理解正确-当调用m1时，对str的引用被复制并传递给将其视为x的函数。运算符当调用m2时，对str的引用被复制并传递给将其视为x的函数。运算符+创建一个新字符串，赋值x=x+"4"只是将x重定向到新字符串，而原始str变量保持不变。对吧？谢谢 最佳答案 String#+::str+other_str→new_strConcatenation—ReturnsanewStringcontainingother_strconc

  10. ruby - rails 3.2.2(或 3.2.1)+ Postgresql 9.1.3 + Ubuntu 11.10 连接错误 - 2

    我正在使用PostgreSQL9.1.3(x86_64-pc-linux-gnu上的PostgreSQL9.1.3，由gcc-4.6.real(Ubuntu/Linaro4.6.1-9ubuntu3)4.6.1，64位编译)和在ubuntu11.10上运行3.2.2或3.2.1。现在，我可以使用以下命令连接PostgreSQLsupostgres输入密码我可以看到postgres=#我将以下详细信息放在我的config/database.yml中并执行“railsdb”，它工作正常。开发:adapter:postgresqlencoding:utf8reconnect:falsedat

随机推荐