User forums > Using Code::Blocks
Debugger issues
Pecan:
Crashes clicking debugger breakpoint red dots have been reported many times and is reported in the berlios bug section.
MortenMacFly:
--- Quote from: oBFusCATed on March 29, 2007, 09:31:05 am ---I was clicking on the red dot to set/unset the breakpoint where the debugger stopped.
There is also an arrow draw at that position. Hope this is enough to reproduce it yourself.
--- End quote ---
I'm sorry, but it isn't. :-( I clicked like hell but nothing happens... Could you provide me with a minimalistic project and a detailed step-by-step instruction?!
@pecan: which bug ID is it?
With regards, Morten.
Pecan:
--- Quote from: MortenMacFly on March 29, 2007, 04:50:37 pm ---
--- Quote from: oBFusCATed on March 29, 2007, 09:31:05 am ---I was clicking on the red dot to set/unset the breakpoint where the debugger stopped.
There is also an arrow draw at that position. Hope this is enough to reproduce it yourself.
--- End quote ---
I'm sorry, but it isn't. :-( I clicked like hell but nothing happens... Could you provide me with a minimalistic project and a detailed step-by-step instruction?!
@pecan: which bug ID is it?
With regards, Morten.
--- End quote ---
My minimalist example is for Linux, but it happened to me about 3 times yesterday on MSW svn 3789.
http://developer.berlios.de/bugs/?func=detailbug&bug_id=9183&group_id=5358
I found where it's happening but never found its cause.
Forum thread:
http://forums.codeblocks.org/index.php/topic,5176.0.html
Though clicking like hell can cause it, it's not always necessary. Yesterday, I just clicked once on the red dot and CB crashed.
It doesn't always happen though. Maybe three times in 20 clicks.
oBFusCATed:
--- Quote from: Pecan on March 29, 2007, 04:06:29 pm ---Crashes clicking debugger breakpoint red dots have been reported many times and is reported in the berlios bug section.
--- End quote ---
Yes I see, I've made the wrong assumption that all debugger bugs goes to the Debugger category in the bug tracker.
--- Quote from: MortenMacFly on March 29, 2007, 04:50:37 pm ---I'm sorry, but it isn't. :-( I clicked like hell but nothing happens... Could you provide me with a minimalistic project and a detailed step-by-step instruction?!
With regards, Morten.
--- End quote ---
No clicking like hell is required 8) and I've tested with slow clicking 1/2 seconds interval between clicks, and with fast one, and the result 100% crashing. The number of clicks is not fixed.
That happend on all projects I've tested.
The minimalistic project is empty console application created with the project wizzard. Just copied the cout line because it didn't stop on the first line.
I'm on gcc 4.1.2 and gdb 6.6
MortenMacFly:
--- Quote from: Pecan on March 29, 2007, 05:28:10 pm ---Though clicking like hell can cause it, it's not always necessary. Yesterday, I just clicked once on the red dot and CB crashed.
It doesn't always happen though. Maybe three times in 20 clicks.
--- End quote ---
Ok - I continued clicking in different frequencies, different number etc.... no crash at all. But: AFAIK this is hardly based on wxScintilla functionality, right? Because I'm not using the C::B's SVN version of wxScintitlla but a more recent (wxcode) one, v1.71.1. Maybe that's the reason why it works for me?
@pecan: You should have the knowledge - so do you mind to update your C::B's wxScintilla to that version and try if the crash still occurs, please?
With regards, Morten.
Navigation
[0] Message Index
[*] Previous page
Go to full version