Author Topic: Unable to stop the debug process  (Read 5354 times)

Offline arnoldo165

  • Single posting newcomer
  • *
  • Posts: 6
Unable to stop the debug process
« on: December 26, 2007, 06:58:22 pm »
Hello,

I used Code::blocks for 5 months and I am fully satisfied with it.
I used version 4719 under Linux Fedora Core 7.
I just came across a problem today that did not occured before :

I can start the program in debug mode but when trying to stop it using the red cross, I receive the message :
"Unable to stop the debug process"
I can see that a gdb process is still running.
Even if I kill it,  I can not switch the debug mode.

I don't know where it comes from.
I tried to reinstall code::blocks using yum. But, the problem remains.
Maybe it is due to the new version of code::blocks that is from december 2007.
Or, more probably, it is due to a corruption of my project.
Do you have an idea of how I can get rid of this problem ?

Thanks a lot,

Arnaud Megret
htp://www.akinator.com

Offline wobien

  • Multiple posting newcomer
  • *
  • Posts: 69
Re: Unable to stop the debug process
« Reply #1 on: December 27, 2007, 11:59:27 am »
Hi,
I have had problems like that (I am using Windows XP), and it turned to be a fatal bug in my own code.
I had to kill the corrupt process in windows taskmanager. I found the bug by putting a break early enough in my program, so that I could catch it before the crash, and then following it step by step until the crash occurred.

Offline arnoldo165

  • Single posting newcomer
  • *
  • Posts: 6
Re: Unable to stop the debug process
« Reply #2 on: December 27, 2007, 12:15:30 pm »
Thank you.

It could be that.
But, in my case, the program does not crash.
I can even debug it, if I put a breakpoint in the code.
What I can not do is just stopping the debugger.
It happens when the program is running and when it is stopped over a breakpoint.
It looks like if C::B is unable to send signal to gdb to stop the program or to kill gdb.

So I must restart C::B after each debug session.
I have the same problem with all my projects under C::B

My gdb is a recent one : version 6.6

Offline arnoldo165

  • Single posting newcomer
  • *
  • Posts: 6
Re: Unable to stop the debug process
« Reply #3 on: December 27, 2007, 05:51:43 pm »
I continued the investigation...

I noticed that C::B version 4719 has been installed by Yum (packet manager for Fedora) on December the 25th, precisely the moment where the problem occurred.
I downgraded C::B to version 3816 and the problem has now disappeared.
But that is not as simple as it seems : I first tried to downgrade for a version (I've forgotten the number) that was installed on my computer before the 4719 and at that time there was no problem.
But the bug was still present after the downgrade.

Well, I may be happy with version 3816. But now, I have no console for standard output/input in debug mode ...  :)
So, I still cannot work on my project.

Thanks for any information tha can help

Arnaud



Offline arnoldo165

  • Single posting newcomer
  • *
  • Posts: 6
Re: Unable to stop the debug process
« Reply #4 on: December 27, 2007, 10:31:53 pm »
Well, it is a bug in code::blocks !!!
http://developer.berlios.de/bugs/?func=detailbug&bug_id=12470&group_id=5358

What sounds strange is why there are so few people encountering the problem...
Are we only two using code::blocks under Linux ? ;-)

Offline rjmyst3

  • Multiple posting newcomer
  • *
  • Posts: 117
    • wxFormBuilder
Re: Unable to stop the debug process
« Reply #5 on: December 28, 2007, 02:31:04 am »
I also encounter this.
I used to be able stop the process, set a breakpoint, and then continue the process.
Now whenever I click the stop button, I get the message box "Unable to stop the debug process"

Ubuntu Gutsy
Code::Blocks 4750

Offline arnoldo165

  • Single posting newcomer
  • *
  • Posts: 6
Re: Unable to stop the debug process
« Reply #6 on: December 28, 2007, 11:46:31 am »
Happy to know I'me not alone in the universe ;-)

I downgraded C::B to version 4280.
The problem is no more present.
I will check from time to time wether the bug is fixed.
It seems that bugs concerning the debugger are rather rapidly corrected.