502555 bugs.kde.org <a name="p-94844-so-i-rebuilt-it-freebsd-stable-142-with-debug-symbols-the-core-file-is-generated-and-still-points-to-qt6-webengine-this-port-refuses-to-build-with-debug-symbols-gdb-shows-nothing-in-the-backtrace-that-i-can-read-address-not-mapped-to-object-sigsegv-segmentation-fault-backtrace-0-some-black-on-black-text-or-a-blank-space-in-at-usrlocallibqt6libqt6webenginecoreso0-1-some-black-on-black-space-or-a-blank-space-then-it-worked-fine-until-kf5-kf6-switched-2" class="anchor" href="#p-94844-so-i-rebuilt-it-freebsd-stable-142-with-debug-symbols-the-core-file-is-generated-and-still-points-to-qt6-webengine-this-port-refuses-to-build-with-debug-symbols-gdb-shows-nothing-in-the-backtrace-that-i-can-read-address-not-mapped-to-object-sigsegv-segmentation-fault-backtrace-0-some-black-on-black-text-or-a-blank-space-in-at-usrlocallibqt6libqt6webenginecoreso0-1-some-black-on-black-space-or-a-blank-space-then-it-worked-fine-until-kf5-kf6-switched-2"> So I rebuilt it [ FreeBSD - stable 14.2 ] with debug symbols. the .core file is generated and still points to qt6-webengine. This port refuses to build with debug symbols. gdb shows nothing in the backtrace that I can read. "address not mapped to object, " SIGSEGV segmentation …

Falkon still segfaults

Paul_Brown April 18, 2025, 11:36am 3

Looks like a more severe case of this

If so, it is a Qt 6.9.0 bug and has been reported.

1 Like