Debugger becomes signal SIGSTOP when started in Qt Creator
-
wrote on 2 Jun 2016, 15:49 last edited by Nozyk_57 6 Feb 2016, 21:30
When I execute my program all works fine. Problem is when I will debugging. Program cannot start, there is popped new window with message
"The inferior stopped becouse it received a signal from the Operating System
Signal name: SIGSTOP
Signal meaning: Stopped (signal)"I use Qt Creator 3.2.1 with Qt 4.8.6 on raspbian.
-
Hi and welcome to devnet,
You should add which version of Qt, Qt Creator and OS your are using.
-
Hi and welcome to devnet,
You should add which version of Qt, Qt Creator and OS your are using.
-
Are you cross-compiling ? Working directly on the Pi ?
-
wrote on 5 Jun 2016, 09:13 last edited by
I'm Working directly on the Pi. I have instaled on Pi dbg, c++, cpp and qt4-default, qtcreator, qt4-dev-tools.
-
Which version of the Pi ?
-
wrote on 6 Jun 2016, 08:06 last edited by
RASPBERRY PI 3 MODEL B, i have made sudo apt-get update and upgrade before and after installation Qt.
-
Can you try to run your debug built application through gdb directly ?
-
wrote on 8 Jun 2016, 16:21 last edited by
Yes I can.
When I try to run debugger on gui app, it works.
I think it's because I run Qt Creator with command "sudo qtcreator", because my console app needs sudo to read/write GPIO. -
Then a better way is to add your current user to the group that has access to the GPIO device. That way there's no need to run Qt Creator as root.
-
wrote on 8 Jun 2016, 20:45 last edited by
I cannot, only root can control GPIO.
-
How are you implementing that control ?
-
wrote on 8 Jun 2016, 21:50 last edited by
I'm make it through wiringPi library.
-
wrote on 12 Dec 2020, 19:04 last edited by
@liprandi Thank you, this worked for me. Although I had different context: I was trying to debug with qtcreator in docker container.
-
wrote on 5 Feb 2021, 04:16 last edited by
Great!! This is always work for me!! Thanks!
-
wrote on 27 Feb 2021, 03:33 last edited by
@liprandi said in Debugger becomes signal SIGSTOP when started in Qt Creator:
@Nozyk_57 You have to UNCHECK the checkbox Project/Run Setting/Run in terminal
I need to run in terminal and debugger worked for me like this, now stopped for some reason. SOlved like mentioned here:
https://forum.qt.io/topic/100958/catching-unix-interrupt-signal-on-console-application-when-debugging-with-qtcreator -
@liprandi said in Debugger becomes signal SIGSTOP when started in Qt Creator:
@Nozyk_57 You have to UNCHECK the checkbox Project/Run Setting/Run in terminal
I need to run in terminal and debugger worked for me like this, now stopped for some reason. SOlved like mentioned here:
https://forum.qt.io/topic/100958/catching-unix-interrupt-signal-on-console-application-when-debugging-with-qtcreatorwrote on 27 Feb 2021, 09:05 last edited by@Aleksey_K
...which is indeed where I suggested telling the debugger to ignore certain signals...