【发布时间】:2013-07-04 02:44:57
【问题描述】:
两次不同的 dlopen 和 dlclose 几次,在 dlopen 上被阻止。
挂在dlopen 上,什么都不输出,cpuidle 降至 0%,无法通过 ctrl+c 退出。
LOG_TRACE("attaching...");
handle = dlopen(plugin_path.c_str(), RTLD_LAZY);
LOG_DEBUG("dlopen called"); // this line did not output, after success couple of times;
然后我使用 gdb attach 到程序:
(gdb) bt
#0 0x0000002a960dbe60 in tcmalloc::ThreadCache::InitTSD () at src/thread_cache.cc:321
#1 0x0000002a960d51bf in TCMallocGuard (this=Variable "this" is not available.) at src/tcmalloc.cc:908
#2 0x0000002a960d5e00 in global constructors keyed to _ZN61FLAG__namespace_do_not_use_directly_use_DECLARE_int64_instead43FLAGS_tcmalloc_large_alloc_report_thresholdE () at src/tcmalloc.cc:935
#3 0x0000002a960fafc6 in __do_global_ctors_aux () at ./src/base/spinlock.h:54
#4 0x0000002a96010f13 in _init () from ../plugins/libmonitor.so
#5 0x0000002a00000000 in ?? ()
#6 0x000000302ad0acaf in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2
#7 0x000000302aff725c in dl_open_worker () from /lib64/tls/libc.so.6
#8 0x000000302ad0aa60 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#9 0x000000302aff79fa in _dl_open () from /lib64/tls/libc.so.6
#10 0x000000302b201054 in dlopen_doit () from /lib64/libdl.so.2
#11 0x000000302ad0aa60 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#12 0x000000302b201552 in _dlerror_run () from /lib64/libdl.so.2
#13 0x000000302b201092 in dlopen@@GLIBC_2.2.5 () from /lib64/libdl.so.2
#14 0x000000000041b559 in uap::meta::MetaManageServiceHandler::plugin_action this=0xb26000, _return=@0x7fbffff500, plugin_name=@0x7fbffff4e0, plugin_path=@0x7fbffff570, t=Variable "t" is not available.)
at /usr/lib/gcc/x86_64-redhat-linux/3.4.5/../../../../include/c++/3.4.5/bits/basic_string.h:1456
#15 0x000000000041b0bc in uap::meta::MetaManageServiceHandler::plugin_action (this=0xb26000, _return=@0x7fbffff500, plugin_name=@0x7fbffff4e0, plugin_path=@0x7fbffff570, t=uap::meta::PluginActionType::RELOAD)
at server/service_handler.cpp:173
#16 0x0000000000417641 in uap::meta::test_Service_Handler_suite_test_case_manage_service_plugin_action_Test::TestBody (this=0xb16080) at test_load.cpp:73
#17 0x00000000004446c6 in testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void> (object=0xb16080, method={__pfn = 0x21, __delta = 0}, location=0x537f30 "the test body")
at ../../../../com/btest/gtest/src/gtest.cc:2744
#18 0x000000000042dd1c in testing::Test::Run (this=0xb16080) at ../../../../com/btest/gtest/src/gtest.cc:2766
#19 0x000000000042e8b4 in testing::TestInfo::Run (this=0xb17160) at ../../../../com/btest/gtest/src/gtest.cc:2958
#20 0x000000000042f415 in testing::TestCase::Run (this=0xb23000, runtype=0) at ../../../../com/btest/gtest/src/gtest.cc:3160
#21 0x0000000000436352 in testing::internal::UnitTestImpl::RunAllTests (this=0xb22000) at ../../../../com/btest/gtest/src/gtest.cc:5938
#22 0x0000000000434299 in testing::UnitTest::Run (this=0x6f4220, run_type=0) at ../../../../com/btest/gtest/src/gtest.cc:5449
#23 0x0000000000434268 in testing::UnitTest::Run (this=0x6f4220) at ../../../../com/btest/gtest/src/gtest.cc:5387
#24 0x0000000000455404 in main (argc=1, argv=0x7fbffff8c8) at ../../../../com/btest/gtest/src/gtest_main.cc:38
其实我已经重新定义了四个函数:
void __attribute__((constructor)) dlinit()
{
}
void __attribute__((destructor)) dldeinit()
{
}
void _init()
{
}
void _fini()
{
}
【问题讨论】:
-
什么程序表现出这种行为,用什么插件?程序和插件是如何构建的?你的
LD_LIBRARY_PATH变量是什么?您的plugin_path是否包含/?它的价值是什么?你应该在上面的代码之后添加一个fflush(NULL);! -
感谢回复,我只是没有设置LD_LIBRARY_PATH,而plugin_path的绝对路径以/开头,是否需要fflush,因为我只是在这里添加了printf,但我的代码没有,这不是fflush的问题, 因为挂在 dlopen
-
我不明白您如何以及为什么认为代码在
dlopen时间挂起?你用调试器了吗?显示插件的代码,以及你的程序的更多代码。 -
LOG_TRACE("正在附加...");句柄 = dlopen(plugin_path.c_str(), RTLD_LAZY); LOG_DEBUG("dlopen 调用"); // 这行没有输出,成功几次后;
-
使用
valgrind检查您的堆是否严重损坏。
标签: linux dlopen shared-libraries