Re: Random crashes when starting some applications with KDE

On Saturday, 17 June 2023 21:00:30 BST Graham Perrin wrote:

> On 17/06/2023 19:48, Mike Clarke wrote:
> > … A problem internal to GDB has been detected, …
> 
> Which version, exactly?

curlew:/var/crash# pkg query %v gdb 
13.1_2
> > This GDB was configured as "x86_64-portbld-freebsd13.1".
> 
> I wonder whether you need to build from source at this time, for
> compatibility with your 13.2-RELEASE.

I've rebuilt gdb from ports but still the same problem

curlew:/var/crash# kgdb /boot/kernel/kernel /var/crash/vmcore.2 
*GNU gdb (GDB) 13.1 [GDB v13.1 for FreeBSD]* 
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-portbld-freebsd13.2". 
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 /boot/kernel/kernel... 
(No debugging symbols found in /boot/kernel/kernel) 
/usr/ports/devel/gdb/work-py39/gdb-13.1/gdb/thread.c:1337: internal-error: 
switch_to_thread: Assertion `thr !=
NULL' failed. 
A problem internal to GDB has been detected, 
further debugging may prove unreliable. 
----- Backtrace ----- 
0x131f681 ??? 
0x17bddf3 ??? 
0x17bdc58 ??? 
0x1c491a3 ??? 
0x177d35f ??? 
0x1454850 ??? 
0x175e67f ??? 
0x1352d94 ??? 
0x178b757 ??? 
0x153b875 ??? 
0x153a29b ??? 
0x1538c9e ??? 
0x122bc74 ??? 
--------------------- 
/usr/ports/devel/gdb/work-py39/gdb-13.1/gdb/thread.c:1337: internal-error: 
switch_to_thread: Assertion `thr !=
NULL' failed. 
A problem internal to GDB has been detected, 
further debugging may prove unreliable. 
Quit this debugging session? (y or n) y 

This is a bug, please report it.  For instructions, see: <https://www.gnu.org/software/gdb/
bugs/>. 

/usr/ports/devel/gdb/work-py39/gdb-13.1/gdb/thread.c:1337: internal-error: 
switch_to_thread: Assertion `thr !=
NULL' failed. 
A problem internal to GDB has been detected, 
further debugging may prove unreliable. 
Unable to dump core, use `ulimit -c unlimited' before executing GDB next time.curlew:/var/
crash# 

... and in case it's relevant here's the configuration details:

(kgdb) show configuration 
This GDB was configured as follows: 
  configure --host=x86_64-portbld-freebsd13.2 --target=x86_64-portbld-freebsd13.2 
            --with-auto-load-dir=$debugdir:$datadir/auto-load 
            --with-auto-load-safe-path=$debugdir:$datadir/auto-load 
            --with-expat 
            --with-gdb-datadir=/usr/local/share/gdb (relocatable) 
            --with-jit-reader-dir=/usr/local/lib/gdb (relocatable) 
            --without-libunwind-ia64 
            --with-lzma 
            --without-babeltrace 
            --without-intel-pt 
            --with-mpfr 
            --with-xxhash 
            --with-python=/usr/local (relocatable) 
            --with-python-libdir=/usr/local/lib (relocatable) 
            --with-debuginfod 
            --without-guile 
            --enable-source-highlight 
            --enable-threading 
            --with-separate-debug-dir=/usr/lib/debug 
-- 
Mike Clarke