MantisBT - Ecere SDK
View Issue Details
0000332Ecere SDKidepublic2010-02-24 22:492014-05-01 02:28
thexa4 
 
immediateminorhave not tried
closedfixed 
 
0.44.080.44.08 
0000332: Debugger Breakpoints Jammed (Initial Step over...)
Debugger Breakpoints Jammed (Initial Step over...)
No tags attached.
related to 0000333closed  Breakpoints not showing up next time reopening project but active 
related to 0000938closed redj gdb doesn't hit on a breakpoint in the beginning of main in x.main.ec when a bp is placed inside __ecere_COM_Initialize 
Issue History
2010-02-24 22:49thexa4New Issue
2010-07-25 20:25redjRelationship addedchild of 0000429
2010-07-26 01:25jeromeNote Added: 0000219
2010-07-26 01:25jeromeStatusnew => feedback
2010-07-26 01:25jeromeRelationship addedrelated to 0000333
2010-07-26 19:10thexa4Target Version => 0.44 draft 2
2010-07-29 15:01jeromeNote Added: 0000290
2010-07-29 15:02jeromeStatusfeedback => new
2010-07-29 15:06jeromePrioritynormal => immediate
2010-12-04 23:24jeromeCategory => Debugger
2012-03-08 15:41redjTarget Versionold 0.44.pre2 => 0.45 Ginkakuji
2012-03-08 17:17redjRelationship deletedchild of 0000429
2012-03-29 07:52redjCategory => ide
2012-03-29 07:52redjProject@3@ => Ecere SDK
2013-04-25 20:15jeromeTarget Version0.45 Ginkakuji => 0.44.5 Debug
2013-07-06 06:32redjRelationship addedrelated to 0000938
2013-08-24 06:42jeromeNote Added: 0000998
2013-08-24 06:42jeromeSeverityfeature => minor
2013-08-24 06:42jeromeStatusnew => closed
2013-08-24 06:42jeromeFixed in Version => 0.44.08
2013-08-24 06:42jeromeTarget Version0.44.50 Debug => 0.44.08
2014-05-01 02:28jeromeResolutionopen => fixed

Notes
(0000219)
jerome   
2010-07-26 01:25   
What exactly does this mean?
Pressing F10 to debug just jam the IDE, or?
(0000290)
jerome   
2010-07-29 15:01   
I tried that in Ubuntu and that does not hit a breakpoint right away.

I will have to try in Windows as well.

It might be something that only happens after a while playing with breakpoints, as it is related to issue 0000333.
(0000998)
jerome   
2013-08-24 06:42   
Closing this issue as it is far from clear/descriptive, and issue most likely related 0000938 was resolved and closed.