Please use QSKIP, so things are properly documented in the log.

Unrelated change?

QSKIP

Was just following what SKIP_IF_ATTACH_FORBIDDEN(); does.

... which though inside KDevMI::isAttachForbidden(...) calls QTest::qSkip(...) :)
Was also initially confused by the name of KDevMI::isAttachForbidden(...) but it is actually from the testhelper part. Someone(tm) should improve that for some explicit namespace or method name...

For the text, i would propose to be more explicit "GDB on FreeBSD produces an unexpected error message, on which KDevelop chokes") and perhaps leave the link to the bug report only as normal comment in the code, not sure how nice multi-line skip messages are in the output?

Please note the actual error directly in the sources, so one does not have to hunt for the commit message or open a browser to read the bug report.

Long nitpicking, let me give a short example how I personally would prefer it: :)

#ifdef Q_OS_FREEBSD
    // Despite successful attach GDB MI spits out a error message "Can't allocate registers". This gets caught by KDevMI layer and gets interpreted as error.
    // PR: https://sourceware.org/bugzilla/show_bug.cgi?id=23464
    QSKIP("GDB on FreeBSD produces an unexpected error message, on which KDevelop chokes");
#endif

That should serve the purpose of keeping the test log short. And allow any reader/editor of the code to directly see what the issue is. What do you think?