Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
configure file to debug codecompletion plugin
ollydbg:
--- Quote from: ollydbg on July 21, 2010, 03:33:58 pm ---
--- Quote from: Pecan on July 21, 2010, 03:29:26 pm ---So, instead of a breakpoint, I place an "asm("int3")" statement at the point I want to begin debugging. CB then loads within 4-10 seconds.
When the int 3 is hit, I then set more breakpoints.
--- End quote ---
Thanks for your reply.
I will test it soon.
--- Quote ---I find when debugging CB devel with CB output that loading is extremely slow when a breakpoint is set.
--- End quote ---
This is too wired...
--- End quote ---
Hi, all, I can fully confirm that when a breakpoint is set before loading, then it will take 90 seconds to debugging CB devel.
But strange that when I set a breakpoint after the loading, the loading time is quite fast(about 10 seconds), then the breakpoint works fine as the first situation. I will report this to the gdb maillist, it is too wired.
As a workaround, can C::B setting breakpoints immediately after loading finishes. :D
oBFusCATed:
--- Quote from: ollydbg on July 21, 2010, 03:41:26 pm ---As a workaround, can C::B setting breakpoints immediately after loading finishes. :D
--- End quote ---
Probably, it can't, but you could try to first run C::B and then attach to it. (There is a chance that the attach will fail, at least in the debugger branch attaching to C::B doesn't work (should fix it, someday))
This behavior looks like a bug in gdb... on linux the starting time of C::B with and without gdb is almost the same (+5 seconds for gdb to load C::B)...
ollydbg:
--- Quote from: oBFusCATed on July 21, 2010, 03:47:37 pm ---This behavior looks like a bug in gdb... on linux the starting time of C::B with and without gdb is almost the same (+5 seconds for gdb to load C::B)...
--- End quote ---
Hi, oBF.
Can you try this on Linux
1, setting some breakpoint on some files (before debugging)
2, start debugging C::B(The debugee "devel" folders) under C::B.
3, see how long the debugee start up.
If without the step 1, the debugee start up really quickly in Windows(5-10 seconds ,with all plugins).
I have read a bit about the gdb source. When gdb load a new symbol file, it will check all the breakpoint to see if the pending breakpoint can be set correctly.
For example, when starting C::B, we have about 40 symbol files to load( include all the plugin shared libraries), every time a shared library and its symbol file are loaded, it will call a function named " breakpoint_re_set ", then all breakpoint will be "re checked", this may cause the time delay.
oBFusCATed:
I've debugged c::b with all plugins (not sure about contrib ones) and I've not seen any difference, so if there is such it is 5-10 sec maximum.
ollydbg:
Thanks.
I think it is a gdb bug on windows. I have reported to both gdb and mingw maillist. Hopefully some gdb guru can fix it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version