-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A bug of the up-to-date develop branch code. #2475
Comments
It's running fine on our docker image built from the latest code (to make sure docker image is up to date, I started a new CI run to build and push the docker image.)
I think the most important stack-trace is the top few lines:
I noticed the bottom few lines have error (probably unrelated to the crash):
This error is Go related, but I don't think it's the error causing the crash. To fix it, can you update your gdb version? According to golang/go#10359 , GDB version < 7.3 will have this problem (GDB 7.3 was released in July of 2011). Back to the problem, The stack-trace shows 766 extern "C" void __once_proxy(void);
767
768 /// call_once
769 template<typename _Callable, typename... _Args>
770 void
771 call_once(once_flag& __once, _Callable&& __f, _Args&&... __args)
772 {
773#ifdef _GLIBCXX_HAVE_TLS
774 auto __bound_functor = std::__bind_simple(std::forward<_Callable>(__f),
775 std::forward<_Args>(__args)...);
776 __once_callable = &__bound_functor;
777 __once_call = &__once_call_impl<decltype(__bound_functor)>;
778#else
779 unique_lock<mutex> __functor_lock(__get_once_mutex());
780 auto __callable = std::__bind_simple(std::forward<_Callable>(__f),
781 std::forward<_Args>(__args)...);
782 __once_functor = [&]() { __callable(); };
783 __set_once_functor_lock_ptr(&__functor_lock);
784#endif
785
786 int __e = __gthread_once(&(__once._M_once), &__once_proxy);
787
788#ifndef _GLIBCXX_HAVE_TLS
789 if (__functor_lock)
790 __set_once_functor_lock_ptr(0);
791#endif
792
793 if (__e)
794 __throw_system_error(__e);
795 }
796#endif // _GLIBCXX_HAS_GTHREADS I can not reproduce the crash on our docker image, so it is fine on Ubuntu 16.04 with GCC 5.4. I suspect it's due to our compiler / linker command changed that caused this crash on some version of OS and GCC. |
已经确认是公司内部jumbo安装的python有问题,自己编译的python2.7可以正常使用,正在找一个合适的安装方式。 |
我用了自己编译的python,同样的问题。python 使用 jumbo下gcc 编译。 |
fixed: #2530 |
现在不编译 go 绕过去这个问题,是不是潜在还是有风险? |
We need to figure out what exactly happened. It works fine on the docker image. I will try to reproduce with Baidu dev machine which uses jumbo. |
@helinwang 对,除了公司默认gcc编译的python有问题,其他所有情况都没有问题,包括docker,mac以及用/opt/compiler下的gcc编译的python。 |
@jacquesqiao noticed 10 hours ago that binaries generated by the GCC installed by Jumbo depend on and binaries generated by and suspected that it's the problem of machine initialization, which installed |
@NHZlX Could you let me know how did you load the debug symbols? When I do $ gdb python
(gdb) run train.py I get:
With no symbols. |
@helinwang |
I have ever met the same problem that debug symbols are missing.
|
When i run the demo of book/03.image_classification, It generates a bug, here is the log:
The problem is here:
here is the gdb log:
I hope it can be settled ASAP, thank you!
The text was updated successfully, but these errors were encountered: