Author Topic: "Break Debugger" button has never worked.  (Read 14836 times)

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: "Break Debugger" button has never worked.
« Reply #15 on: December 15, 2013, 02:09:42 pm »
Please post full build log from the debugger, so I can take a look at it.

I can't create ARM project use the wizard. Do you have the same thing?.....
Do you have the scripted wizard plugin installed and enabled?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline zeroth

  • Multiple posting newcomer
  • *
  • Posts: 27
Re: "Break Debugger" button has never worked.
« Reply #16 on: December 18, 2013, 06:25:36 am »
I'm going to be regularly checking back at this thread every few days or so. This is a feature I'm really looking forward to using once it's fixed (pause debugger). If you prefer, I can submit a bug report.


edit: it seems I already posted about this a year ago and forgot about it; http://developer.berlios.de/bugs/?func=detailbug&group_id=5358&bug_id=18759
« Last Edit: December 18, 2013, 06:28:31 am by zeroth »

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 3353
Re: "Break Debugger" button has never worked.
« Reply #17 on: December 18, 2013, 10:30:26 am »
have you read the reply of oBFusCATed? also the comment on your bug report:
Quote
Can you paste the full debugger log? (see in the settings how to enable it).

Also when this happens you can kill the gdb process, which is child of C::B, not the whole C::B.

Also do older revisions work correctly in this situation? In other words is this a regression or it has been broken forever?

please reply to this posts, because we need more information...

Offline zeroth

  • Multiple posting newcomer
  • *
  • Posts: 27
Re: "Break Debugger" button has never worked.
« Reply #18 on: December 19, 2013, 09:44:17 pm »
I thought oBFusCATed's last reply in this thread was to liss719 since I had already posted a debugger log. I'll post up a fresh debugger log when I get a chance.

I didn't realize the report had been replied to until I re-discovered it. I'll copy the information I've given here over to the bug report. It'll take me a bit before I get a chance though.
« Last Edit: December 19, 2013, 09:47:54 pm by zeroth »