Re: espeakup stops speaking bookworm arm64
- To: James Addison <jay@jp-hosting.net>
- Cc: tommym2006@gmail.com, Frank Carmickle <frank@carmickle.com>, Debian Accessibility Team <debian-accessibility@lists.debian.org>, jason@jasonjgw.net
- Subject: Re: espeakup stops speaking bookworm arm64
- From: Geoff Shang <geoff@QuiteLikely.com>
- Date: Wed, 20 Dec 2023 20:21:17 +0200 (IST)
- Message-id: <[🔎] ce59faf2-e3ae-2ebe-3f1b-bddff0c7b171@QuiteLikely.com>
- In-reply-to: <CALDQ5NxrCVx_HnPiyefoNLWYGFdp4tjSsEt-jmm1EytMV6Bg5A@mail.gmail.com>
- References: <CALDQ5NyqYYmXrFUhC33T4wC_e73bon1aiXYqxJa36=AwZnJWmg@mail.gmail.com> <187F5D01-153D-4189-ACB7-D190FBA03458@carmickle.com> <8B35183D-653A-4B69-8F0D-04C7FF98C88A@carmickle.com> <CALDQ5Nxj0mVc38sBnLfy6enmbLo7HLkpXVBvHKwPy=fF=kc58A@mail.gmail.com> <04BEC44B-6C70-42F6-857F-0EA74B28E92D@carmickle.com> <CALDQ5NzdnohO3hn0qtD8Os134tMzYRP4Gj-KgJ3AQsvDoOo2wQ@mail.gmail.com> <B39CE658-29D3-458C-B866-9B92257E67C8@carmickle.com> <CALDQ5NxrFEbqM68m=rFvr6N-eqs1AkfjQoY2qKywsD6Vjg0OkA@mail.gmail.com> <086C6A6B-1321-4952-A7E3-B4B266F86F7C@carmickle.com> <CALDQ5Nx7PuEvLLoq3trv96S4N_LTfxpfoW57dE_EEOrLc_sN-g@mail.gmail.com> <CALDQ5NwOtccgxJ8NgQWD1resZipAWj1AZ5dz9s4Mw=HU-SfVAg@mail.gmail.com> <a4f2611f-3218-9d4b-bb4a-630a372a1121@QuiteLikely.com> <CALDQ5NxBxC9H7uqp7mtP+YPHpy8jhjZ9=pJzp6f+jpEMnmCuNA@mail.gmail.com> <022801da217f$75036190$5f0a24b0$@gmail.com> <CALDQ5NxrCVx_HnPiyefoNLWYGFdp4tjSsEt-jmm1EytMV6Bg5A@mail.gmail.com>
On Tue, 28 Nov 2023, James Addison wrote:
To do that, the first step is to enable a sources.list entry for debug
symbol packages, then to install the gdb and espeakup-dbgsym packages,
and then after the espeakup process stops speaking, to attach the gdb
debugger to locate where it got stuck by running: gdb
/usr/bin/espeakup <pid-of-broken-process>
If that works and you are provided with a (gdb) shell, you should be
able to type the single word 'bt' and press enter to get a backtrace,
and then copy and paste the results here.
It took me a couple of goes, and I lost speech entirely both times (not
sure why), but I got a trace.
I'm not sure how helpful it is though.
root@debian:~# gdb /usr/bin/espeakup 861
GNU gdb (Debian 13.1-3) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/espeakup...
Reading symbols from /usr/lib/debug/.build-id/76/62ad26e5f970e59309a544f3864db114aa389e.debug...
Attaching to program: /usr/bin/espeakup, process 861
[New LWP 862]
[New LWP 863]
[New LWP 864]
[New LWP 865]
[New LWP 866]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007f9de46bfda6 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x00007f9de46bfda6 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f9de46c4b33 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x00005605c505e734 in main (argc=<optimized out>, argv=<optimized out>)
at ../src/espeakup.c:229
Cheers,
Geoff.
Reply to: