I am sending you this email because I encounter a problem with Debian
Buster and default Qt5 package.
I installed packages below :
Í‚· debian 10.8 x86_64 (amd64)
Í‚· apt-get install build-essentials
Í‚· apt-get install gdb
Í‚· apt-get install qt5-default
Í‚· apt-get install qtcreator
I have tried to debug an application which contains a thread with GBD but
GDB stops when thread starts. I tried to build GDB with last sources but
the problem still remains.
*This problem doesnÍ¢€™t exist with Debian 9 *with the same procedure of
installation.
You can find a simple example which increments a counter in a thread every
500ms at the URL below https://pastebin.com/WegsL9vd.
Do you know if there is a way to solve this problem ?
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:"Calibri",sans-serif"><span style="color:rgb(31,73,125)">I am sending you this email because I
encounter a problem with Debian Buster and default Qt5 package.</span><span><span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:"Calibri",sans-serif"><span style="color:rgb(31,73,125)">I have tried to debug an application
which contains a thread with GBD but GDB stops when thread starts. I tried to
build GDB with last sources but the problem still remains.</span><span><span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:"Calibri",sans-serif"><span style="color:rgb(31,73,125)"><u>This problem doesnÍ¢€™t exist with
Debian 9 </u>with the same procedure of installation. <br></span></p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:"Calibri",sans-serif"><span style="color:rgb(31,73,125)">You can find a simple example which increments a
counter in a thread every 500ms at the URL below <a href="https://pastebin.com/WegsL9vd">https://pastebin.com/WegsL9vd</a>.</span><span><span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:"Calibri",sans-serif"><span style="color:rgb(31,73,125)">Do you know if there is a way to solve
this problem͂ ?</span><span><span></span></span></p>
Cette action est irreversible, confirmez la suppression du commentaire ?
Signaler le commentaire
Veuillez sélectionner un problème
Nudité
Violence
Harcèlement
Fraude
Vente illégale
Discours haineux
Terrorisme
Autre
Lisandro Damián Nicanor Pérez Meyer
Hi Vincent! On Tue, 30 Mar 2021 at 05:29, Vincent charente wrote:
Dear All, I am sending you this email because I encounter a problem with Debian Buster and default Qt5 package. I installed packages below : · debian 10.8 x86_64 (amd64) · apt-get install build-essentials · apt-get install gdb · apt-get install qt5-default
This one is really not needed at all, feel free to remove it.
· apt-get install qtcreator I have tried to debug an application which contains a thread with GBD but GDB stops when thread starts. I tried to build GDB with last sources but the problem still remains. This problem doesn’t exist with Debian 9 with the same procedure of installation. You can find a simple example which increments a counter in a thread every 500ms at the URL below https://pastebin.com/WegsL9vd. Do you know if there is a way to solve this problem ?
In fact I can reproduce your issue and at the same time I can make it work under gdb itself, so the issue seems to be in Qt Creator. I've reproduced the issue with Qt Creator from unstable, so let me suggest you to file a bug upstream: http://https://bugreports.qt.io Do not forget to upload this test code, it's very straightforward and so a nice example for an upstream issue. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Hi Vincent!
On Tue, 30 Mar 2021 at 05:29, Vincent charente <vincecharente@gmail.com> wrote:
Dear All,
I am sending you this email because I encounter a problem with Debian Buster and default Qt5 package.
I installed packages below :
· debian 10.8 x86_64 (amd64)
· apt-get install build-essentials
· apt-get install gdb
· apt-get install qt5-default
This one is really not needed at all, feel free to remove it.
· apt-get install qtcreator
I have tried to debug an application which contains a thread with GBD but GDB stops when thread starts. I tried to build GDB with last sources but the problem still remains.
This problem doesn’t exist with Debian 9 with the same procedure of installation.
You can find a simple example which increments a counter in a thread every 500ms at the URL below https://pastebin.com/WegsL9vd.
Do you know if there is a way to solve this problem ?
In fact I can reproduce your issue and at the same time I can make it
work under gdb itself, so the issue seems to be in Qt Creator. I've
reproduced the issue with Qt Creator from unstable, so let me suggest
you to file a bug upstream: http://https://bugreports.qt.io Do not
forget to upload this test code, it's very straightforward and so a
nice example for an upstream issue.
Hi Vincent! On Tue, 30 Mar 2021 at 05:29, Vincent charente wrote:
Dear All, I am sending you this email because I encounter a problem with Debian Buster and default Qt5 package. I installed packages below : · debian 10.8 x86_64 (amd64) · apt-get install build-essentials · apt-get install gdb · apt-get install qt5-default
This one is really not needed at all, feel free to remove it.
· apt-get install qtcreator I have tried to debug an application which contains a thread with GBD but GDB stops when thread starts. I tried to build GDB with last sources but the problem still remains. This problem doesn’t exist with Debian 9 with the same procedure of installation. You can find a simple example which increments a counter in a thread every 500ms at the URL below https://pastebin.com/WegsL9vd. Do you know if there is a way to solve this problem ?
In fact I can reproduce your issue and at the same time I can make it work under gdb itself, so the issue seems to be in Qt Creator. I've reproduced the issue with Qt Creator from unstable, so let me suggest you to file a bug upstream: http://https://bugreports.qt.io Do not forget to upload this test code, it's very straightforward and so a nice example for an upstream issue. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Lisandro Damián Nicanor Pérez Meyer
Hi again! On Tue, 30 Mar 2021 at 09:55, Lisandro Damián Nicanor Pérez Meyer wrote:
[snip]
In fact I can reproduce your issue and at the same time I can make it work under gdb itself, so the issue seems to be in Qt Creator. I've reproduced the issue with Qt Creator from unstable, so let me suggest you to file a bug upstream: http://https://bugreports.qt.io Do not forget to upload this test code, it's very straightforward and so a nice example for an upstream issue.
Actually it is not an issue but a feature. Qt Creator is stopping the execution when it receives a signal from gdb, in this case SIGSTOP. Add a breakpoint inside the thread code and press F5 to start debugging. If you accept the message and press F10 (step) some times you will be able to reach the code. You can tell Qt Creator to ignore the signal. Check https://forum.qt.io/topic/100958/catching-unix-interrupt-signal-on-console-application-when-debugging-with-qtcreator/2 I've added handle SIGSTOP pass nostop noprint And it just worked :-) -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Hi again!
On Tue, 30 Mar 2021 at 09:55, Lisandro Damián Nicanor Pérez Meyer
<perezmeyer@gmail.com> wrote:
[snip]
In fact I can reproduce your issue and at the same time I can make it
work under gdb itself, so the issue seems to be in Qt Creator. I've
reproduced the issue with Qt Creator from unstable, so let me suggest
you to file a bug upstream: http://https://bugreports.qt.io Do not
forget to upload this test code, it's very straightforward and so a
nice example for an upstream issue.
Actually it is not an issue but a feature. Qt Creator is stopping the
execution when it receives a signal from gdb, in this case SIGSTOP.
Add a breakpoint inside the thread code and press F5 to start
debugging. If you accept the message and press F10 (step) some times
you will be able to reach the code.
You can tell Qt Creator to ignore the signal. Check
https://forum.qt.io/topic/100958/catching-unix-interrupt-signal-on-console-application-when-debugging-with-qtcreator/2
Hi again! On Tue, 30 Mar 2021 at 09:55, Lisandro Damián Nicanor Pérez Meyer wrote:
[snip]
In fact I can reproduce your issue and at the same time I can make it work under gdb itself, so the issue seems to be in Qt Creator. I've reproduced the issue with Qt Creator from unstable, so let me suggest you to file a bug upstream: http://https://bugreports.qt.io Do not forget to upload this test code, it's very straightforward and so a nice example for an upstream issue.
Actually it is not an issue but a feature. Qt Creator is stopping the execution when it receives a signal from gdb, in this case SIGSTOP. Add a breakpoint inside the thread code and press F5 to start debugging. If you accept the message and press F10 (step) some times you will be able to reach the code. You can tell Qt Creator to ignore the signal. Check https://forum.qt.io/topic/100958/catching-unix-interrupt-signal-on-console-application-when-debugging-with-qtcreator/2 I've added handle SIGSTOP pass nostop noprint And it just worked :-) -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
In fact I can reproduce your issue and at the same time I can make it work under gdb itself, so the issue seems to be in Qt Creator. I've reproduced the issue with Qt Creator from unstable, so let me suggest you to file a bug upstream: http://https://bugreports.qt.io Do not forget to upload this test code, it's very straightforward and so a nice example for an upstream issue.
Actually it is not an issue but a feature. Qt Creator is stopping the
execution when it receives a signal from gdb, in this case SIGSTOP.
Add a breakpoint inside the thread code and press F5 to start
debugging. If you accept the message and press F10 (step) some times
you will be able to reach the code.
You can tell Qt Creator to ignore the signal. Check
<div dir="ltr"><div>Hi Lisandro,</div><div><br></div><div>Great, it works with handle SIGSTOP pass nostop noprint. I think I had already tried but I forgot "pass".</div><div><br></div><div>Thank you very much<br>
In fact I can reproduce your issue and at the same time I can make it work under gdb itself, so the issue seems to be in Qt Creator. I've reproduced the issue with Qt Creator from unstable, so let me suggest you to file a bug upstream: http://https://bugreports.qt.io Do not forget to upload this test code, it's very straightforward and so a nice example for an upstream issue.