Hi,sorry for the delay. I've attacked the stack, it was always evaluating the same property again.
This is qbs at 20de9f301.
Am 13.06.2024 um 00:44 schrieb Иван Комиссаров:
What’s the actual stack? Ivan12 июня 2024 г., в 23:03, Björn Schäpers <qt-maill...@hazardy.de> написал(а): Hi, okay I debugged into it, it's a stack overflow from something completely different. I wonder why the release variant only crashed with the module provider in place. I did try to replicate the issue with a small example, but the problem did not show. So I can't give you anything. Nevertheless thanks, Björn. Am 12.06.2024 um 10:41 schrieb Иван Комиссаров:Hello. The usual. Build Qbs in debug mode and run in the debugger, possibly with --jobs=1. Or attach to the running Qbs Session in QtC/vscode. Alternatively, if you code is public, provide a link to repo to reproduce and we can take a look. Ivan12 июня 2024 г., в 00:31, Björn Schäpers <qt-maill...@hazardy.de> написал(а): Hi, I've created a module that reads a xml file and exports some of the content through properties, that works nice. I wanted to extend it, so that there is a (predefined) choice of xml files, and one could depend on multiple of these. So I thought a module provider would be the right choice. I have setup the provider, but qbs crashes on the load() of the xml document, a console.info() before is still printed, afterwards not anymore. I've even changed the provider to just depend on the old module and then it also crashes, while the module itself still works if a product depends on it directly. How can I debug what's happening here? Kind regards, Björn. _______________________________________________ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
stack.txt.zst
Description: Binary data
_______________________________________________ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs