Qt Creator fails to recognize the GDB whose version output contains extra numbers
-
So it's a Qt Creator issue. The version string contains extra stuff that trips the parser. Hence the wrong version shown in the dialog.
I created QTCREATORBUG-34887 to track it.
Patch in progress. -
Both GDBs are built by crosstool-NG. Their version output is as follows:
./aarch64-linux-gnu-gdb --version GNU gdb (crosstool-NG 1.29.0_rc2) 17.2 Copyright (C) 2025 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../aarch64-linux-gnu-gdb --version GNU gdb (GDB) 17.2 Copyright (C) 2025 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.The only difference is the text inside the parentheses -- one say 'crosstool-NG 1.29.0_rc2', the another says 'GDB'.
-
Hi,
What output do you get if you call each of them with
--configuration? -
The 'crosstool-NG' GDB output is shown as follows:
./aarch64-linux-gnu-gdb --configuration This GDB was configured as follows: configure --host=x86_64-build_pc-linux-gnu --target=aarch64-linux-gnu --with-auto-load-dir=$debugdir:$datadir/auto-load --with-auto-load-safe-path=$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=/home/devel/workspace/staging/aarch64-linux-gnu-ct-ng/share/gdb (relocatable) --with-jit-reader-dir=/home/devel/workspace/staging/aarch64-linux-gnu-ct-ng/lib/gdb (relocatable) --without-libunwind-ia64 --with-lzma --without-babeltrace --without-intel-pt --without-xxhash --with-python=/usr --with-python-libdir=/usr/lib --without-debuginfod --with-curses --without-guile --without-amd-dbgapi --disable-source-highlight --enable-threading --enable-tui --without-system-readline --with-separate-debug-dir=/home/devel/workspace/staging/aarch64-linux-gnu-ct-ng/lib/debug (relocatable) --with-sysroot=/home/devel/workspace/staging/aarch64-linux-gnu-ct-ng/aarch64-linux-gnu/sysroot (relocatable) ("Relocatable" means the directory can be moved with the GDB installation tree, and GDB will still find it.) GNU Readline library version: 8.2 (internal) -
The 'GDB' GDB output is shown as follows:
./aarch64-linux-gnu-gdb --configuration This GDB was configured as follows: configure --host=x86_64-build_pc-linux-gnu --target=aarch64-linux-gnu --with-auto-load-dir=$debugdir:$datadir/auto-load --with-auto-load-safe-path=$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=/home/devel/workspace/staging/aarch64-linux-gnu/share/gdb (relocatable) --with-jit-reader-dir=/home/devel/workspace/staging/aarch64-linux-gnu/lib/gdb (relocatable) --without-libunwind-ia64 --with-lzma --without-babeltrace --without-intel-pt --without-xxhash --with-python=/usr --with-python-libdir=/usr/lib --without-debuginfod --with-curses --without-guile --without-amd-dbgapi --disable-source-highlight --enable-threading --enable-tui --without-system-readline --with-separate-debug-dir=/home/devel/workspace/staging/aarch64-linux-gnu/lib/debug (relocatable) --with-sysroot=/home/devel/workspace/staging/aarch64-linux-gnu/aarch64-linux-gnu/sysroot (relocatable) ("Relocatable" means the directory can be moved with the GDB installation tree, and GDB will still find it.) GNU Readline library version: 8.2 (internal) -
So it's a Qt Creator issue. The version string contains extra stuff that trips the parser. Hence the wrong version shown in the dialog.
I created QTCREATORBUG-34887 to track it.
Patch in progress. -
Patch integrated :-)
If you need it earlier, you might want to consider building the debugger plugin for your version of Qt Creator. If not Qt Creator itself directly. -
Or to add to @SGaist: Use one of the next snapshots from: https://download.qt.io/snapshots/qtcreator/21.0/21.0.0-beta1 which will contain the fix.
Regards
-
Or to add to @SGaist: Use one of the next snapshots from: https://download.qt.io/snapshots/qtcreator/21.0/21.0.0-beta1 which will contain the fix.
Regards
-
N novum has marked this topic as solved


