Re: espeakup stops speaking version 1:0.90-11

[Frank Carmickle <frank@carmickle.com>]

Greetings Jason et al.

On Mar 21, 2023, at 11:28, Jason White <jason@jasonjgw.net> wrote:
> Can you log in remotely and attach gdb to the espeak process when it's not speaking but (obviously) before you kill it? Then obtain a backtrace. You might need to install debug symbols for espeakup. Debian has separate packages for those.
> 
> The syntax would be
> gdb /usr/bin/espeakup <process-id>

Here's the output inside gdb after espeakup stops talking.


/build/gdb-yCDzia/gdb-13.1/gdb/thread.c:85: internal-error: inferior_thread: Assertion `current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
0xaaaab9c39b9b ???
0xaaaab9f7cefb ???
0xaaaab9f7d0e3 ???
0xaaaaba124873 ???
0xaaaab9f36ebb ???
0xaaaab9e8f49b ???
0xaaaab9b8a2bf ???
0xaaaab9f31a37 ???
0xaaaab9f31f47 ???
0xaaaab9f31ff7 ???
0xaaaab9e382d7 ???
0xffffa6b35387 _td_fetch_value
./nptl_db/fetch-value.c:115
0xffffa6b3230f td_ta_map_lwp2thr
./nptl_db/td_ta_map_lwp2thr.c:194
0xaaaab9dc7d8f ???
0xaaaab9dc9347 ???
0xaaaab9f33e73 ???
0xaaaab9d9081f ???
0xaaaab9d9c033 ???
0xaaaaba124d03 ???
0xaaaaba1257f7 ???
0xaaaab9f40787 ???
0xaaaab9dd8dd3 ???
0xaaaab9ddb513 ???
0xaaaab9ddb733 ???
0xaaaab9b81183 ???
0xffffb0de777f __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
0xffffb0de7857 __libc_start_main_impl
../csu/libc-start.c:381
0xaaaab9b873af ???
0xffffffffffffffff ???
---------------------

Do we now need to debug the debugger?

Thanks all,
--FC