Debugger becomes signal SIGSTOP when started in Qt Creator

Nozyk_57

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.

SGaist

Hi and welcome to devnet,

You should add which version of Qt, Qt Creator and OS your are using.

Nozyk_57

@SGaist added.

SGaist

Are you cross-compiling ? Working directly on the Pi ?

Nozyk_57

I'm Working directly on the Pi. I have instaled on Pi dbg, c++, cpp and qt4-default, qtcreator, qt4-dev-tools.

SGaist

Which version of the Pi ?

Nozyk_57

RASPBERRY PI 3 MODEL B, i have made sudo apt-get update and upgrade before and after installation Qt.

SGaist

Can you try to run your debug built application through gdb directly ?

Nozyk_57

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.

SGaist

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.

Nozyk_57

I cannot, only root can control GPIO.

SGaist

How are you implementing that control ?

Nozyk_57

I'm make it through wiringPi library.

liprandi

@Nozyk_57 You have to UNCHECK the checkbox Project/Run Setting/Run in terminal

nicktrandafil

@liprandi Thank you, this worked for me. Although I had different context: I was trying to debug with qtcreator in docker container.

CKShih

Great!! This is always work for me!! Thanks!

Aleksey_K

@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

JonB

@Aleksey_K
...which is indeed where I suggested telling the debugger to ignore certain signals...