https://bugs.kde.org/show_bug.cgi?id=436958
Kyle Johnson <kylej61...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kylej61...@gmail.com
--- Comment #14 from Kyle Johnson <kylej61...@gmail.com> ---
So this bug has also been reported in Gentoo here:
https://bugs.gentoo.org/789330
Apparently the issue comes in with merge request 5
(https://invent.kde.org/sdk/kdiff3/-/merge_requests/5). If you look at the
added chk_connect_x macros defined in src/defmac.h, they all rely on the
QCONNECT_ASSERT macro which is defined as the following:
#ifndef NDEBUG
#define QCONNECT_ASSERT(COND_) Q_ASSERT(COND_)
#else
#define QCONNECT_ASSERT(COND_) COND_
#endif
I'm not particularly versed in KDE/QT development, but does Q_ASSERT(COND_)
resolve to nothing in release code? If so, then it would seem plausible that
not defining NDEBUG would result in Q_ASSERT being used in the QCONNECT_ASSERT
macro, resulting in all of the chk_connect_x macros resolving to nothing and
thus not connecting any of the signals.
In the Gentoo bug report, the user uploaded a patch reverting all of the
chk_connect macros to straight up connect() calls and that seemed to resolve
the issue. Presumably, defining NDEBUG would have the same result.
--
You are receiving this mail because:
You are watching all bug changes.
