Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Speedup GDB debugging

(1/3) > >>

BlueHazzard:
If you are on windows you may know the problem:
Debugging with GDB is PAINFULLY slow...
I finally have found a 10 year old workaround: https://stackoverflow.com/questions/27380443/why-is-gdb-so-slow-in-windows
To use this in codeblocks:
1) Settings-> Environment-> Environment Variables->Add:
Key =
--- Code: ---_NO_DEBUG_HEAP
--- End code ---
Value =
--- Code: ---1
--- End code ---
2) Ok
3) Project->Properties->EnvVars option->Select environment....->defaukt

For me this is speeding up the gdb startup fo 200%

ollydbg:
I meet the same issue before. Especially if you code has many "new" and "delete" function calls, GDB will be quite slow.

Setting such environment variable will speed up the debugee a lot!

Miguel Gimenez:
Step 3 generates an "EnVars Plugin Warning, The project contained a reference to an envvar set ('default') that could not be found".

AndrewCot:
With my latest local build I do not get the warnings when setting up step 3, but if I go back into Project->Properties I get the warning. The EnvVars options tab shows the correct data as does the Settings-> Environment-> Environment Variables dialog data.

The warning is also shown when I go back into the Settings-> Environment-> Environment Variables and exit (it shows 3 times...).

The warning dialog info is:
[Window Title]
EnvVars Plugin Warning

[Content]
Warning: The project contained a reference to an envvar set
('default') that could not be found.

[OK]

Hope this extra info is of some help.

Miguel Gimenez:
I think the EnvVars plugin is buggy, whatever set you select in Project->Properties->EnvVars options is never found.

Navigation

[0] Message Index

[#] Next page