Is it possible to have a segment fault because of the QML debugging ?
-
I was experiencing a very weird event: a segmentation fault at every execution of the debugger. Initially, I thought I'd messed up a
QHashI was using heavily. I used the debugger and step-by-step tool so extensively that I hadn't attempted a real execution for hours.Then, I noticed that the segfault happened even when the debugging was paused. This made me suspicious, so i first tried to stop the debug at the very start of the program on the main and it still crashed even if it was on pause. And i started to notice a correlation bettwen the time of the segfault and the time the local variable view took to load.
So I tried to execute the program without the debugger, and it worked fine. When closing the expression evaluator, it still crashed, but once I cleared the expressions, it stopped crashing.So, my question is: is it supposed to be possible to cause a segmentation fault with the Expression Evaluator tab?
Or am i the choosen one, the only one able to segfault the world, unable to download Qt5, destroyer of nativ C++ library, the one unable to use a slot for a connectI didn't manage to recover the exact expression that caused the segfault because I deleted them all, but I think it was something like a
QHashwith only one entry, cast into its key. -
I was experiencing a very weird event: a segmentation fault at every execution of the debugger. Initially, I thought I'd messed up a
QHashI was using heavily. I used the debugger and step-by-step tool so extensively that I hadn't attempted a real execution for hours.Then, I noticed that the segfault happened even when the debugging was paused. This made me suspicious, so i first tried to stop the debug at the very start of the program on the main and it still crashed even if it was on pause. And i started to notice a correlation bettwen the time of the segfault and the time the local variable view took to load.
So I tried to execute the program without the debugger, and it worked fine. When closing the expression evaluator, it still crashed, but once I cleared the expressions, it stopped crashing.So, my question is: is it supposed to be possible to cause a segmentation fault with the Expression Evaluator tab?
Or am i the choosen one, the only one able to segfault the world, unable to download Qt5, destroyer of nativ C++ library, the one unable to use a slot for a connectI didn't manage to recover the exact expression that caused the segfault because I deleted them all, but I think it was something like a
QHashwith only one entry, cast into its key.@AntGP said in Is it possible to have a segment fault because of the QML debugging ?:
So, my question is: is it supposed to be possible to cause a segmentation fault with the Expression Evaluator tab?
Sadly I have seen this reported here previously. There was one such a few(?) months ago. Might have been a widgets application and might have been an assertion failure, but something similar to yours. I believe that may have been reported for fixing, as I think Creator is not "supposed" to "crash" on an expression evaluation.
-
@AntGP @JonB I think it is https://forum.qt.io/topic/161612/qt-creator-crashes-sigabrt-on-expression-error and that already links to a bugreport: https://bugreports.qt.io/browse/QTCREATORBUG-32747
You can comment and vote there.
Qt has to stay free or it will die.
-
@AntGP @JonB I think it is https://forum.qt.io/topic/161612/qt-creator-crashes-sigabrt-on-expression-error and that already links to a bugreport: https://bugreports.qt.io/browse/QTCREATORBUG-32747
You can comment and vote there.
-
A AntGP has marked this topic as solved
-
@AntGP said in Is it possible to have a segment fault because of the QML debugging ?:
i don't see any button
Did you log-in?
