KDAB / GammaRay

GammaRay is a tool to poke around in a Qt-application and also to manipulate the application to some extent.
https://www.kdab.com/gammaray
Other
1.59k stars 279 forks source link

debug probe fatal message #737

Open AdamP-2 opened 1 year ago

AdamP-2 commented 1 year ago

I have built the Gammaray from source code, cloned by master at commit 0fbfb4ba. I am building for qt 6.3.1 on windows 11.

I built gammaRay with the following arguments from within the gammaRay directory:

I could then create an installer of gammaRay. I also created a debug probe with the following steps

and installed the debug probe as well

running GammaRay now I can find and attach to both debug and release versions of qt apps, however there are certain gammaRay tabs that don't work when attached to debug probes. If I try and use any of the following tabs Widgets/Timers/Models/Signals/System/Styles with a debug build, I get the following Q_ASSERT ASSERT: "addr != Protocol::InvalidObjectAddress"

image

This happens with even QtCreator code examples (Qt Creator 8.0.1 - Qt Widgets - Application example) and because I can still use Messages/Meta Objects/Meta Types tabs, I am logging this as an issue. if you need the installers I have built please let me know

Below is the full backtrace:

handleMessage (C:/Users/User/gamma2/core/tools/messagehandler/messagehandler.cpp:71) QFileInfo::filePath QFileInfo::filePath QFileInfo::filePath QFileInfo::filePath GammaRay::PropertySyncer::handleMessage (C:/Users/User/gamma2/common/propertysyncer.cpp:107) GammaRay::PropertySyncer::qt_static_metacall (C:/Users/User/gamma2/build/Release/common/gammaray_common_autogen/include_Debug/EWIEGA46WW/moc_propertysyncer.cpp:88) QFileInfo::filePath QFileInfo::filePath GammaRay::Endpoint::dispatchMessage (C:/Users/User/gamma2/common/endpoint.cpp:351) GammaRay::Server::messageReceived (C:/Users/User/gamma2/core/remote/server.cpp:202) GammaRay::Endpoint::readyRead (C:/Users/User/gamma2/common/endpoint.cpp:158) QtPrivate::FunctorCall<QtPrivate::IndexesList<>,QtPrivate::List<>,void,void (cdecl GammaRay::Endpoint::*)(void)>::call (C:/Qt/6.3.1/msvc2019_64/include/QtCore/qobjectdefs_impl.h:171) QtPrivate::FunctionPointer<void (cdecl GammaRay::Endpoint::)(void)>::call<QtPrivate::List<>,void> (C:/Qt/6.3.1/msvc2019_64/include/QtCore/qobjectdefs_impl.h:209) QtPrivate::QSlotObject<void (__cdecl GammaRay::Endpoint::)(void),QtPrivate::List<>,void>::impl (C:/Qt/6.3.1/msvc2019_64/include/QtCore/qobjectdefs_impl.h:420) QFileInfo::filePath QFileInfo::filePath QFileInfo::filePath QFileInfo::filePath QNetworkInterface::interfaceNameFromIndex QNetworkInterface::interfaceNameFromIndex QNetworkInterface::interfaceNameFromIndex QNetworkInterface::interfaceNameFromIndex QNetworkInterface::interfaceNameFromIndex QLineEdit::default constructor closure' QLineEdit::default constructor closure' QFileInfo::filePath QFileInfo::filePath QFileInfo::filePath CallWindowProcW DispatchMessageW QFileInfo::filePath QTextCharFormat::setFontLetterSpacingType QFileInfo::filePath QFileInfo::filePath QFileInfo::filePath QTextCharFormat::setFontLetterSpacingType QLineEdit::`default constructor closure' main (C:/Qt/Examples/Qt-6.3.1/widgets/mainwindows/application/main.cpp:77) WinMain (C:/Users/qt/work/qt/qtbase/src/entrypoint/qtentrypoint_win.cpp:97) invoke_main (D:/a/_work/1/s/src/vctools/crt/vcstartup/src/startup/exe_common.inl:107) __scrt_common_main_seh (D:/a/_work/1/s/src/vctools/crt/vcstartup/src/startup/exe_common.inl:288) __scrt_common_main (D:/a/_work/1/s/src/vctools/crt/vcstartup/src/startup/exe_common.inl:331) WinMainCRTStartup (D:/a/_work/1/s/src/vctools/crt/vcstartup/src/startup/exe_winmain.cpp:17) BaseThreadInitThunk RtlUserThreadStart

mattkdab commented 4 months ago

@AdamP-2 are you still having this issue on current master? if so please provide the installers and any relevant updated information. i ran into some issues with my windows environment trying to reproduce, so the installers will likely be helpful. doesn't appear to be reproducible on linux

shzm-li commented 4 months ago

I can't reproduce this on the current master on Windows with Qt6.6 probes.