Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Patch for codeblocks 20.03 adding multi columns in memory dump
MicroSourceCode:
Work on the patch is completed, I managed to raise performance, which had a positive effect on the speed of debugging. In the future, I plan to make a plugin with viewing the memory region depending on the window size, this will dramatically increase the debugging speed, since the debugger will only need to draw a small piece of memory.
oBFusCATed:
I don't think this is a good idea. The debugger should be made to be faster. Which could be done with the gdb/mi protocol or implementing direct support for lldb. Hopefully I'll find time to start work on the latter.
I hope, I'll find some time soon, so I can finish the review.
oBFusCATed:
--- Quote from: MicroSourceCode on March 05, 2021, 11:40:19 am ---Work on the patch is completed, I managed to raise performance, which had a positive effect on the speed of debugging.
--- End quote ---
I don't see any new commits in the pull request. Where is this new work?
MicroSourceCode:
The commit can be made if the patch is checked on popular systems, Windows and linux, etc. For this I posted the patches. Testers welcome! If there is a positive result on different systems, then I will create a commit. On my debian buster, the result is positive. I will not install Windows and other systems on my computer to test this.
MicroSourceCode:
I noticed that if I use debug mode all the time, the program starts to consume memory. That is, I edit the source, turn on debugging, make changes to the source and start debugging again. I think this is due to the fact that the debugger windows constantly remain in memory and this is clearly somehow connected with the work of wxwidget, it is quite possible that a memory leak occurs in wxwidget. What tools can be used to find the leak?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version