[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overfl
From: |
Eli Zaretskii |
Subject: |
bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow |
Date: |
Tue, 22 Mar 2022 16:36:42 +0200 |
> From: Fernando de Morais <fernandodemorais.jf@gmail.com>
> Date: Tue, 22 Mar 2022 10:50:44 -0300
> Cc: 54458@debbugs.gnu.org, bandali@gnu.org
>
> Well, I've never debugged an error like this, especially using GDB, but
> attached are some logs that I managed to capture:
>
> - The ``backtrace.log'' is just the standard output that shows when
> Emacs crashes after the multiple C stack overflow messages;
> - The ``core.3183'' one is the output of the `coredumpctl info <PID>'
> command; and
> - The ``gdb_bt_emacs_core.3183.log'' one is the backtrace output from
> gdb of the previous core dump.
It seems that your Emacs binary is stripped of debug symbols, so the
backtrace produced by GDB is not useful. can you rebuild without
stripping, or download and install the missing debug symbols
somewhere? Then repeat the experiment and post the backtrace.
Thanks.
bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow, Mattias Engdegård, 2022/03/27
- bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow, Mattias Engdegård, 2022/03/28
- bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow, Eli Zaretskii, 2022/03/28
- bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow, J.P., 2022/03/28
- bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow, Mattias Engdegård, 2022/03/29
- bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow, Eli Zaretskii, 2022/03/29
- bug#54458: 27.2; erc-dcc-get: Re-entering top level after C stack overflow, Mattias Engdegård, 2022/03/29