On Mar 25, 2023, at 13:45, Jason White <jason@xxxxxxxxxxxx> wrote: > > On 25/3/23 13:27, Frank Carmickle wrote: >> That's nasty. What happens if you run Espeakup within gdb from the beginning? >> It doesn't speak at all. I may just not know what I'm doing in the debugger. > Did you use the run command to start execution of the program once it was loaded in the debugger? You can supply any desired command line options. Thank you for spelling that out for me. I thought I needed to tell it to execute somehow. Quite unfortunately this is what happens. Reading symbols from /usr/bin/espeakup... Reading symbols from /usr/lib/debug/.build-id/2c/a5375523b29da3b9abcab61d402b5d1d074942.debug... (gdb) run Starting program: /usr/bin/espeakup --default-voice=en [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1". /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 ----- 0xaaaac8be9b9b ??? 0xaaaac8f2cefb ??? 0xaaaac8f2d0e3 ??? 0xaaaac90d4873 ??? 0xaaaac8ee6ebb ??? 0xaaaac8e3f49b ??? 0xaaaac8b3a2bf ??? 0xaaaac8ee1a37 ??? 0xaaaac8ee1f47 ??? 0xaaaac8ee1ff7 ??? 0xaaaac8de82d7 ??? 0xffff7a885387 _td_fetch_value ./nptl_db/fetch-value.c:115 0xffff7a88230f td_ta_map_lwp2thr ./nptl_db/td_ta_map_lwp2thr.c:194 0xaaaac8d77d8f ??? 0xaaaac8d79347 ??? 0xaaaac8ee3e73 ??? 0xaaaac8d3a8a7 ??? 0xaaaac8d4b82f ??? 0xaaaac90d4d03 ??? 0xaaaac90d57f7 ??? 0xaaaac8d89d0f ??? 0xaaaac8d8b737 ??? 0xaaaac8b31183 ??? 0xffff8026777f __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 0xffff80267857 __libc_start_main_impl ../csu/libc-start.c:381 0xaaaac8b373af ??? 0xffffffffffffffff ??? --------------------- /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. Copying the speakup mailing list also, as I think William might be hanging out there too. The back story is that I'm having an issue where espeakup stops speaking. It appears to do so completely randomly. I'm seeing it on multiple installations, arm64 now. I have seen this before on amd64 also. I've been using it under both vmware Fusion, amd64, and now qemu arm64. I will do some testing on bare metal to see if there's any impact. Does anyone have any ideas? Thanks all, --FC
