QT opens disassembler when debugging
-
@Nocksen said in QT opens disassembler when debugging:
I dont see anythin important in the logs
Can you show it?
wrote on 18 Jul 2018, 16:29 last edited by -
@Nocksen
/home/.../Schreibtisch/C++/1.Programmierung mit C++/Kapitel 5/3.Übungen 1-14/build-Uebung3-Desktop_Qt_5_11_1_GCC_64bit-Debug/Uebung3
Try using a project (and build) directory without spaces and without Umlauts (only ASCII characters).
I'm pretty sure that's the reason.
Regards
-
wrote on 18 Jul 2018, 16:51 last edited by
@aha_1980 Thanks, that was the problem :)
-
@aha_1980 Thanks, that was the problem :)
wrote on 18 Jul 2018, 18:00 last edited by@Nocksen if your issue is solved please don't forget to mark your post as such. Thanks
-
FYI: I created https://bugreports.qt.io/browse/QTCREATORBUG-20834 to get a warning message for such cases.
-
@aha_1980 I try all things you have said, making directory without spaces.
but still I have that problem with my debugger.Hi @Neotod,
then please show the debugger log (Windows > Views).
Also provide the needed information about operating system, Qt and Creator version, used compiler, 32 or 64 bit.
Have you tried a minimal example?
Regards
-
wrote on 6 Jan 2021, 20:28 last edited by Mehdi Karimi 1 Jun 2021, 20:35
Hi,
I installed Ubuntu 20.04 today. Then I installed Qt 5.15.2. I have the disassembler issue. Then I removed whole Qt and install a fresh Qt6. The issue is still there. I do not use space or any special character in my build directory. I have the same issue like https://imgur.com/a/aUf0354
compiler: gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Debuger: GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2It always shows disassembler when debuger reaches std::async(std::lunch::async,....) function!!!(But maybe unrelataed).
Even I upgrade gcc to 10. The problem still is there.
-
wrote on 6 Jan 2021, 21:37 last edited by
I had the same disassembler issue until I noticed there was a breakpoint set for the Kate editor, for some mysterious reason. I cleared all breakpoints and returned to business as usual.
-
I had the same disassembler issue until I noticed there was a breakpoint set for the Kate editor, for some mysterious reason. I cleared all breakpoints and returned to business as usual.
wrote on 6 Jan 2021, 22:07 last edited by@Psnarf How did you remove all break point from Kate editor and what is kate editor or where is it? I add
handle SIGSTOP nopass
handle SIGSTOP nostopoptions to my GDB debuger to not receive those stops. But please let me know where is the kate and how did you remove its beak points.
-
wrote on 9 Feb 2021, 08:58 last edited by
Hello,
By removing #line directives i have fixed this issue.
-