Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Debugger sometimes doesn't delete breakpoints

<< < (4/5) > >>

theven:

--- Quote from: oBFusCATed on December 11, 2012, 06:26:30 pm ---Probably the code is inlined in many translation units and the breakpoint is inserted many times.
But I've not seen any commands to delete the breakpoint from your log.
Please do a session reproducing the exact bug you see. And when the breakpoint is hit for the second time execute the gdb command "info breakpoints".

--- End quote ---
It is not inserting many times, because phantom breakpoint place do not depend on where the normal points.

I do not understand what "hit for the second time" means. A point is always, if there is at least one other point.

Debugger full log with "info breakpoints" after hit.
http://www.everfall.com/paste/id.php?gsb8d80b8zas

That is interesting:
Debugger stops at the point in line 143. But info is displayed point only in lines 102, 104, 106, where at the moment I have is my real points ...and, method begin for all three , but in lines 102, 104 and 106 i have code of Constructor

--- Code: ---98.
99. explicit DynamicArrayImplStack(ConstIteratorType first, ConstIteratorType last):
100. mSize( std::distance(first, last) )
101. {       // I have breakpoint there
102. if(mSize == 0) return;
103.     // there
104. newBufferAllocateForElements(mSize);
105. // and there
106. ElementCopier<T>::CopyElementsArrayNewPlace(*first, data(), mSize);
107. }
108.
--- End code ---
As you can see this code has nothing to do with the begin(), 102 for sure. :)

For reasons of clarity, I left only 102, all in exactly the same.
http://www.everfall.com/paste/id.php?5zd4rteraejt

oBFusCATed:
Try to disable function inlining and verify you're using -O0 or no optiomizations.

theven:

--- Quote from: oBFusCATed on December 11, 2012, 09:07:03 pm ---Try to disable function inlining and verify you're using -O0 or no optiomizations.

--- End quote ---
Of course I'm building exactly, without any optimizations, only raw code for debugginig.
 
--- Code: ---g++ -include "Precompiled.h"  -g -Wshadow -Winit-self -Wredundant-decls -Wcast-align -std=c++0x -Wall -pipe -fPIC -fvisibility=hidden
--- End code ---

theven:
I'm sure this is not related with code and inlining, because phantom point continues to appear in the same place at the debug even after setting of the breakpoints in another place, rebuilding workspace and rebooting the system. Also, it probably is related to the CB, because the point is moving with the code while shifting code in the editor. Let's try: tell me where it is stored raw information about breakpoints, I will show you the file. After I remove it and then try to find a order of actions for reliable reproduction of the problem (for the problem occurs).

oBFusCATed:

--- Quote from: theven on December 13, 2012, 12:20:37 am ---Let's try: tell me where it is stored raw information about breakpoints, I will show you the file. After I remove it and then try to find a order of actions for reliable reproduction of the problem (for the problem occurs).

--- End quote ---
What about trying another thing?
Open a console window, then try to debug you program using command line gdb. I'm sure you'll get the same behaviour.

Navigation

[0] Message Index

[#] Next page

[*] Previous page