Skip to content
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

Signal handler is not async safe #359

Open
rossmacgregor opened this issue Mar 10, 2016 · 0 comments
Open

Signal handler is not async safe #359

rossmacgregor opened this issue Mar 10, 2016 · 0 comments

Comments

@rossmacgregor
Copy link

Signal hander should be async safe to avoid deadlocks. Thread sanitizer is reporting that new is being calling inside the signal handler.

WARNING: ThreadSanitizer: signal-unsafe call inside of a signal (pid=25902)
#0 operator new(unsigned long) :0 (OamTest+0x0000000f26cd)
#1 void std::__1::vector<Test::LogMessage, std::__1::allocatorTest::LogMessage >::__push_back_slow_pathTest::LogMessage(Test::LogMessage&&) :0 (OamTest+0x000000291ac7)
#2 Test::TestLogWriter::WriteInfo(std::__1::basic_string<char, std::__1::char_traits, std::_1::allocator > const&, char const, int) :0 (OamTest+0x00000028f20a)
#3 (anonymous namespace)::SignalHandler(int) :0 (OamTest+0x00000028c2d9)
#4 _tsan::CallUserSignalHandler(tsan::ThreadState, bool, bool, int, my_siginfo_t, void) :0 (OamTest+0x0000000ff381)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant