Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Patch for codeblocks 20.03 adding multi columns in memory dump
oBFusCATed:
I don't see any UI for it, so I guess it is something new. This was my question actually.
Note: There is the "Value Tooltip Font" option. If you want to add a font setting do it in a similar fashion.
BlueHazzard:
--- Quote from: oBFusCATed on February 14, 2021, 02:35:29 pm ---
--- Quote from: oBFusCATed on February 14, 2021, 01:19:07 am ---Because they are expensive? I think you've requested it this way.
I'm not sure memory watches and examine memory should be treated the same way using the same API, but I might be wrong.
--- End quote ---
@bluehazzard: Another reason might be that the request update is expected to come from the UI. Somewhere in your plugin you'll have to probably request an update when you detect that the cursor has changed.
--- End quote ---
Yea, i found out today... It would really help to add some comments to the events to indicate when they are fired.... because i was thinking cbEVT_DEBUGGER_PAUSED was send when the debugger halts, and i can request the memory, but i was wrong, i have to listen an cbEVT_DEBUGGER_CURSOR_CHANGED event...
MicroSourceCode:
I have installed cbMemoryView plugin, is it only for windows system? On debian system I rename file cbMemoryWatch_unix.cbp in cbMemoryView_unix.cbp. Changed the lines containing MemoryWatch to MemoryView and added lib aui depending. Fixed some shortcomings in the plugin, while it cannot serve as a complete replacement for memorydump. As an addition.
ollydbg:
Something maybe off topic, but I'm interested in view the memory as an image.
I'm mainly developing image processing algorithm, such as OpenCV's cv::Mat.
I would like to view the image in the debugger. Some years ago, I use the GDB's pretty printer to fetch the debugee's memory, and construct a image.
See my project page here: https://sourceforge.net/projects/visualdebugger/
I would like find a way to directly view the memory as an image, I'm not sure GDB's CLI(command line interface) can pass image raster bytes to C::B, or maybe, we need to use some TCP connection from C::B to the debugger(or the customized python pretty printer)
Any suggestions?
Thanks.
oBFusCATed:
You'll have to write a plugin for this or somehow expand the watches view or some other kind of view, but I doubt it will be reliable without too much effort.
Keep in mind that the current debugger plugin is going to the recycling bin, hopefully it will happen this year, but I don't promise anything. :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version