search

scylladb / seastar

High performance server-side application framework
http://seastar.io
Apache License 2.0
8.38k stars 1.55k forks source link

scylla-gdb will demangler failed when compile in debug mode #247

Open flabby opened 7 years ago

flabby commented 7 years ago

Hi, I'm new to seastar.

When I compile with $SEASTAR/build/debug/seastar.pc instead of release one, 

# install dependency
# ninja compile
ninja-build -d stats -d explain -d keeprsp  -v

c++ `pkg-config --cflags --libs $SEASTAR/build/debug/seastar.pc` getting-started.cc

scylla-gdb will core dump.

/opt/scylladb/bin/gdb a.out

The error message is below.

Reading symbols from a.out...../../gdb/cp-support.c:1595: demangler-warning: unable to demangle '_ZSt7forwardIRP12continuationIZN6futureIJEE12then_wrappedIZN12app_template14run_deprecatedEiPPcOSt8functionIFvvEEEUlOT_E0_S2_EET0_SC_EUlSC_E_JEEESC_RNSt16remove_referenceISB_E4typeE' (demangler failed with signal 11)
Attempting to dump core.
../../gdb/cp-support.c:1608: demangler-warning: unable to demangle '_ZSt7forwardIRP12continuationIZN6futureIJEE12then_wrappedIZN12app_template14run_deprecatedEiPPcOSt8functionIFvvEEEUlOT_E0_S2_EET0_SC_EUlSC_E_JEEESC_RNSt16remove_referenceISB_E4typeE' (demangler failed with signal 11)
A problem internal to GDB has been detected,
further debugging may prove unreliable.

Thanks for your time.

tgrabiec commented 7 years ago

This is a known bug in demangler (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68700).

But doesn't it ask whether to continue the session? It is supposed to allow you to continue past this error.

gleb-cloudius commented 7 years ago

On Tue, Feb 21, 2017 at 12:52:12AM -0800, Tomasz Grabiec wrote:

This is a known bug in demangler (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68700).

But doesn't it ask whether to continue the session? It is supposed to allow you to continue past this error.

Not for a debug build IIRC, but I did not try for along time now.

-- Gleb.

nyh commented 7 years ago

On Tue, Feb 21, 2017 at 10:52 AM, Tomasz Grabiec notifications@github.com wrote:

This is a known bug in demangler (https://gcc.gnu.org/bugzilla/ show_bug.cgi?id=68700).

According to that issue, it is caused by https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78252 and that bug was resolved with a patch. If that patch didn't end up in distributions yet, can we include it in the Scylla version of gdb?