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

Crash in symbolize_unittest on Ubuntu 18.04 x86_64 #435

Closed
emmenlau opened this issue Feb 25, 2019 · 3 comments
Closed

Crash in symbolize_unittest on Ubuntu 18.04 x86_64 #435

emmenlau opened this issue Feb 25, 2019 · 3 comments

Comments

@emmenlau
Copy link

I get the following backtrace from a crash in symbolize_unittest on Ubuntu 18.04 x86_64 with gcc-7.3:

#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007ffff7264801 in __GI_abort () at abort.c:79
#2  0x000055555556e7e1 in google::DumpStackTraceAndExit () at /data/Debug/glog-0.3.5/src/utilities.cc:152
#3  0x0000555555562a3b in google::LogMessage::Fail () at /data/Debug/glog-0.3.5/src/logging.cc:1488
#4  0x0000555555566a9a in google::LogMessage::SendToLog (this=0x7fffffffd9c0) at /data/Debug/glog-0.3.5/src/logging.cc:1442
#5  0x000055555556279e in google::LogMessage::Flush (this=0x7fffffffd9c0) at /data/Debug/glog-0.3.5/src/logging.cc:1311
#6  0x0000555555562f43 in google::LogMessageFatal::~LogMessageFatal (this=<optimized out>, __in_chrg=<optimized out>)
    at /data/Debug/glog-0.3.5/src/logging.cc:2023
#7  0x0000555555560b7d in TestWithPCInsideNonInlineFunction () at /data/Debug/glog-0.3.5/src/symbolize_unittest.cc:315
#8  0x0000555555560d8c in main (argc=<optimized out>, argv=<optimized out>) at /data/Debug/glog-0.3.5/src/symbolize_unittest.cc:353

I build with default cmake flags, and with gflags installed.

@samhartlebury
Copy link

I am having a similar problem with the symbolize unit test on windows 7 too...
Always fails.. .

@samhartlebury
Copy link

Update...
It passes unit tests in debug mode but not release? What is this craziness?

@emmenlau
Copy link
Author

I can not reproduce the problem with glog 0.4.0 anymore. Closing as fixed(?)

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

2 participants