Qt Creator 18 not showing debug fault reason information.
-
Hi!
Started using Qt Creator recently and I am very happy with it! Using it for C and C++.But when debugging, it will not display the reason for the debug fault break signal. I tried looking through different views but the only information I found was INFERIOR SPONTANEOUS STOP buried in the Debugger Log windows pile of unformatted JSON.
Is there any way I can get to see the reason for the break? This is really hard to debug without knowing what has happened. Or can I access GDB/LLDB console directly so I can query the reason?
Let me know!
-
Hi!
Started using Qt Creator recently and I am very happy with it! Using it for C and C++.But when debugging, it will not display the reason for the debug fault break signal. I tried looking through different views but the only information I found was INFERIOR SPONTANEOUS STOP buried in the Debugger Log windows pile of unformatted JSON.
Is there any way I can get to see the reason for the break? This is really hard to debug without knowing what has happened. Or can I access GDB/LLDB console directly so I can query the reason?
Let me know!
@Sosowski You will have to give more details. Windows or Linux? Both GDB and LLDB behave like this?
-
Sure! My apologies, I am not sure what's the intended behaviour supposed to be here, as I only started using it.
This is Qt Creator 18.0.0 using Qt 6.10.1 on openSUSE Tumbleweed Linux, KDE Plasma 6.5.3 on X11. It's LLDB, but I have no idea how to select GDB, there is nothing in the option
I have found an interactive Debugger Log view, but it's showing me raw JSON optputs in two windows (command window and output window). Looks like this:
>@ >token("113")@ >@ >Running debugger command "version"@ >@ >success="1",output="lldb version 21.1.6\n",error=""@I'll look up LLDB docs to see how I can query for past events, but it's a bit of a pain working with this weird json-like output.
EDIT: The only information I can find in the logs is details="None",stop-reason="signal",state="unknown" And the weird stricture makes it impossible to read.
-
Sure! My apologies, I am not sure what's the intended behaviour supposed to be here, as I only started using it.
This is Qt Creator 18.0.0 using Qt 6.10.1 on openSUSE Tumbleweed Linux, KDE Plasma 6.5.3 on X11. It's LLDB, but I have no idea how to select GDB, there is nothing in the option
I have found an interactive Debugger Log view, but it's showing me raw JSON optputs in two windows (command window and output window). Looks like this:
>@ >token("113")@ >@ >Running debugger command "version"@ >@ >success="1",output="lldb version 21.1.6\n",error=""@I'll look up LLDB docs to see how I can query for past events, but it's a bit of a pain working with this weird json-like output.
EDIT: The only information I can find in the logs is details="None",stop-reason="signal",state="unknown" And the weird stricture makes it impossible to read.
@Sosowski You might have to install
gdbfrom the package manager.Then you would have to change the debugger in the Kit's settings.
