-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
InstallFailureSignalHandler can not get the detailed stack errors #777
Comments
ubuntu 18.04 kint@kint:~/SoftInstall/3rd/glog$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.5.0-3ubuntu1~18.04' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) |
Hi @kintzhao I use the same test code, and the same environment, but I still can get the full stack trace, and cannot reproduce the issue.
|
@fdgkhdkgh Thanks for looking into the issue. @kintzhao You seem to be confusing a detailed stack trace with symbol resolution. There's clearly a detailed stack trace present. What is missing are symbol names. Given your problem is not reproducible, you need to find out why symbols are not resolved in your particular case. |
$ uname -a $ lsb_release -a $ g++ -v |
kint@kint:/tmp/test$ file test |
kint@kint:/tmp/test$ g++ -ggdb test.cpp -lglog -o test |
Let me close the issue since your problem cannot be reproduced and we're already preparing the 0.6 release. You can test glog 0.6.0-rc1 and report back in case you still observe the issue and provide a full reproducer, i.e. a |
this is my test code: test.cpp, glog is v0.5.0
build :
g++ -g -O3 test.cpp -lglog -o test
My result Output, But it has not the detailed stack error!
Test by the reference Google glog prints no stack trace
The text was updated successfully, but these errors were encountered: