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
GDB segfaults when debugging anything using kj-async or CAPNP_DEBUG_TYPES #191
Comments
Yeah, I run into this all the time and it's really annoying. There is a work-around, though:
|
Also here is a previous bug report for the same problem: |
kentonv
changed the title
Cannot debug anything that uses Cap'nProto with GDB
GDB segfaults when debugging anything using kj-async or CAPNP_DEBUG_TYPES
Mar 16, 2015
Thanks, didn't think about disabling demangling. |
(Thanks to @mortehu for introducing me to the work-around.) |
I believe this has long been fixed in gdb. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The symbol kj::Quantity<decltype(((long)(1)) * ((long)(1))), kj::::NanosecondLabel> kj::operator*<long, long, kj::::NanosecondLabel>(long, kj::Quantity<long, kj::_::NanosecondLabel>) causes GDB (and c++filt) to crash while demangling it: https://sourceware.org/bugzilla/show_bug.cgi?id=18133. While this is an upstream bug in binutils, it makes it impossible to debug my application. It would be really nice if a workaround could be found.
The text was updated successfully, but these errors were encountered: