Author Topic: Patch for codeblocks 20.03 adding multi columns in memory dump  (Read 6388 times)

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Patch for codeblocks 20.03 adding multi columns in memory dump
« on: February 11, 2021, 10:37:16 am »
Patch for codeblocks 20.03 and svn improves the Memory Dump dockable dialog. I added a list box to it to select the number of columns to display. Something like this is done in modern IDEs like AVR studio and other... This is useful for debugging microcontrollers, viewing commands in their binary format, and more compact display of data. Can select the following number of columns to display: 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32.

In comparison with the original, the display of the address of the first line has been corrected, the end line will also be shown, as a rule it is smaller in some modes.

The wxTextCtrl element has been replaced with wxListBox, which made it possible to refuse to scroll down the list and more conveniently observe the data.

link to patch:
https://github.com/MicroSourceCode/cb20.03-MemoryDump
« Last Edit: March 14, 2021, 07:57:42 pm by MicroSourceCode »

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 2974
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #1 on: February 11, 2021, 03:26:29 pm »
Hi!
Thank you for your work.
Can you please create a ticket in sourceforge? This would help us and prevent it getting lost in the forum.

Thank you again!

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #2 on: February 12, 2021, 06:16:42 pm »
Can you please create a ticket in sourceforge?

Ok, I will try to register on sourceforge and create a ticket.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #3 on: February 12, 2021, 06:22:43 pm »
This is not a strict requirement. You can also prepare a pull request on my repo if it is easier for you.
https://github.com/obfuscated/codeblocks_sf
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #4 on: February 12, 2021, 08:09:06 pm »
It is not difficult for me to adapt the patch for the svn version. There are no big differences.

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #5 on: February 13, 2021, 08:48:23 am »
I have sent a pull request to github, if everything goes well, it will appear in an updated version of the program. ;)


Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 2974
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #6 on: February 13, 2021, 07:05:53 pm »
just for reference:
https://github.com/bluehazzard/cbMemoryView

This is a memory view with tabs for multiple memory views

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 2974
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #7 on: February 14, 2021, 12:56:48 am »
Ok, i found out that memoryWatches are not updated on cursor change?
@Obfuscated do you remember why?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #8 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.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #9 on: February 14, 2021, 10:05:28 am »
just for reference:
https://github.com/bluehazzard/cbMemoryView

This is a memory view with tabs for multiple memory views

Thank, this very good plugins for memory watch.
What new things are planned to be added to codeblocks? What is the development strategy of the program?
 
 

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #10 on: February 14, 2021, 11:03:10 am »
What new things are planned to be added to codeblocks? What is the development strategy of the program?
We're not an organisation, so there is no common plan/goal. We're just separate developers working on whatever everybody likes.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #11 on: February 14, 2021, 12:25:27 pm »
On monitor 1920x1080, fonts in debugger windows very small, how temp solution I insert everywhere:

int FontSize = c->ReadInt(wxT("/common/font_size_dialog"), 10);
    wxFont font(FontSize, wxFONTFAMILY_MODERN, wxFONTSTYLE_NORMAL, wxFONTWEIGHT_NORMAL);
    m_pText->SetFont(font);                                           

Is there any other solution?
 


Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #12 on: February 14, 2021, 02:27:21 pm »
What is wxT("/common/font_size_dialog")?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #13 on: February 14, 2021, 02:35:29 pm »
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.

@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.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #14 on: February 14, 2021, 06:51:41 pm »
What is wxT("/common/font_size_dialog")?

This custom option in default.conf

<debugger_common>
                <common>
                        <disassembly>
                                <MIXED_MODE bool="0" />
                        </disassembly>
                        <examine_memory>
                                <SIZE_TO_SHOW int="128" />
                                <COLUMNS_TO_SHOW int="10" />
                        </examine_memory>
                        <AUTO_BUILD bool="1" />
                        <AUTO_SWITCH_FRAME bool="1" />
                        <DEBUG_LOG bool="0" />
                        <JUMP_ON_DOUBLE_CLICK bool="0" />
                        <REQUIRE_CTRL_FOR_TOOLTIPS bool="0" />
                        <PERSPECTIVE int="2" />
                        <FONT_SIZE_DIALOG int="14" />
                </common>

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #15 on: February 14, 2021, 08:29:41 pm »
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.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 2974
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #16 on: February 14, 2021, 10:29:05 pm »
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.

@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.
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...

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #17 on: February 15, 2021, 08:44:05 am »
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.

« Last Edit: February 15, 2021, 08:46:26 am by MicroSourceCode »

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5353
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #18 on: February 18, 2021, 04:13:29 pm »
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.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #19 on: February 18, 2021, 08:51:06 pm »
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. :)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #20 on: February 21, 2021, 10:28:09 am »
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.

Is it a memory pointer? If a pointer is present then the pretty printer can handle this memory. TCP connection will be significantly slower, do you want to process the data stream through wxwidget to display it?

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5353
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #21 on: February 22, 2021, 05:08:03 am »
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.

Is it a memory pointer? If a pointer is present then the pretty printer can handle this memory. TCP connection will be significantly slower, do you want to process the data stream through wxwidget to display it?

No, it is not a memory pointer, it is just a normal variable. Let me explain below:

There are mainly 3 parts, each part has a seperate process.

The first part is the debugee, where the cv::Mat resides. It is just a normal variable which has the type cv::Mat.
The second part is the GDB, where I can run the Python pretty printer to fetch the debugee's memory, the memory is usually huge, for example, a 1000*1000 pixel image, one byte for each pixel, then it is 1M bytes.
The third part is the Code::Blocks or the debugger plugin, which communicates with GDB by pipes(stderr, stdout, stdin).

I would like the show the image in the debugger plugin, so I need to find a way to pass the huge memory(1M bytes in my example) from the GDB to Code::Blocks. I'm not sure it is OK to through the command pipes, I think this will pollute the norman command line based communication. So, I would find a way such as using TCP.

BTW: the reason I would like to show the image in Code::Blocks' process is that I can show the image in GDB's process(by using the Python's GUI), if GDB is running, those GUI will hang.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #22 on: February 22, 2021, 12:46:56 pm »
Quite intricate. Don't want to use BlueHazzard's memory interface? Take the memory you want, then do something like this:

Mat image (1920, 1080, CV_8UC3);
typedef cv :: Point3_ <uint8_t> Pixel;
// first. raw pointer access.
for (int r = 0; r <image.rows; ++ r) {
    Pixel * ptr = image.ptr <Pixel> (r, 0);
    const Pixel * ptr_end = ptr + image.cols;
    for (; ptr! = ptr_end; ++ ptr) {
        ptr->x = 255;
    }

and convert cv::Mat to wxBitmap for output to window. This is simplified, the data can be compressed.

https://github.com/PBfordev/wxopencvtest
« Last Edit: February 22, 2021, 01:53:31 pm by MicroSourceCode »

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5353
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #23 on: February 22, 2021, 03:37:29 pm »
Quite intricate. Don't want to use BlueHazzard's memory interface? Take the memory you want, then do something like this:

If I understand correctly, BlueHazzard's memory interface just use the GDB's memory dump command Memory (Debugging with GDB).

Normally, a cv::Mat has a header part and follows the GRAY/RGB raster color byte array. I can find the start address of the raster byte array, and construct a wxBitmap.

The only concern is that I'm not sure if dump a huge memory(for example, a 5M byte memory) is possible. Will it cause slow down of GDB pipes?
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #24 on: February 22, 2021, 06:08:29 pm »
It will be slow, because of the slow communication (mostly on the C::B site) between C::B and gdb.
But the biggest problem is that you don't have an easy way to show an image in C::B from the debugger.
You could probably do this in gdb-python-only by making a command which stores an image on disc every time you execute it. After that you could use your favourite image viewer to inspect it.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #25 on: February 24, 2021, 02:06:05 pm »
How slow, only an experiment can show, for example, copying 10 mb of any data.
At the moment, the start of displaying an image is possible only by modifying the program code itself. This is not particularly difficult, you need to write a procedure that receives input and output from the debugger and runs the callback function, as an example, you can see how this is done for the CPU Registers dialog and other debugger windows.

Ideally, the codeblocks program should have a generic approach for doing this, providing the ability to custom filter input and output from the debugger for plugins.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #26 on: February 24, 2021, 07:26:32 pm »
How slow, only an experiment can show, for example, copying 10 mb of any data.
I know it is slow. Especially if gdb prints the data on multiple rows as it likes to do. :)
Also I know why it happens. :)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #27 on: February 26, 2021, 08:25:47 am »
I changed the behavior of my patch, now the memory dump list remembers its previous position, and returns to this position during step-by-step debugging. Here is the code for wxTextCtrl:

int w, h, clientHeight;
       m_pText->GetClientSize(&w, &h);

       clientHeight = (h + (h % m_pText->GetCharHeight())) / m_pText->GetCharHeight();
       unsigned maxScrollPosition = m_pText->GetScrollRange(wxVERTICAL)- h + 2;
       unsigned position = m_pText->GetScrollPos(wxVERTICAL);

       if ( position < maxScrollPosition )
       {
           int result = position / m_pText->GetCharHeight() + clientHeight;
                          int parttext, col;
                          parttext = m_pText->GetLineLength(m_pText->GetNumberOfLines() / 2) + 1;

                          col = result < m_result ? m_result - result : result - m_result;

                          if  ( col > 2 )
                               m_result = result;

     m_pText->ShowPosition(m_result * parttext - parttext + 1);

The code works correctly on my machine, if the font of the list is 10 pt or more, if less then it can be easily adapted.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5353
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #28 on: February 26, 2021, 03:49:56 pm »
Some more information, there is a project: OpenImageDebugger, which can show in-memory OpenCV image or Eigen matrix, I see it has some code to run a TCP server, it's GUI is based on QT.

Another Visual studio visual debugger plugin awulkiew/graphical-debugging: GraphicalDebugging extension for Visual Studio, which can show many in memory data(such as int array, matrix)
« Last Edit: February 26, 2021, 03:52:56 pm by ollydbg »
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #29 on: February 26, 2021, 06:04:49 pm »
OpenImageDebugger uses the same technology as the pretty printer, you need to define the variable for watch manually, or make an interface for this. As for the visual debugger plugin, I can't say anything.


Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #30 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. 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.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #31 on: March 05, 2021, 05:22:15 pm »
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.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #32 on: March 05, 2021, 11:54:58 pm »
Work on the patch is completed, I managed to raise performance, which had a positive effect on the speed of debugging.
I don't see any new commits in the pull request. Where is this new work?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #33 on: March 06, 2021, 01:50:07 pm »
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.


Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #34 on: March 06, 2021, 03:42:32 pm »
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?
« Last Edit: March 06, 2021, 03:44:53 pm by MicroSourceCode »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #35 on: March 06, 2021, 04:11:51 pm »
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.
What are you talking about?
You've started this https://github.com/obfuscated/codeblocks_sf/pull/16 pull request.
I've reviewed it, I've showed you some things which should be improved before merging.
Are you going to do the work required to finish this pull request?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #36 on: March 17, 2021, 05:57:53 pm »
I have not received a request.

Last change, adding an error message to the end of the wxListBox. Disadvantage, when changing the display of columns, the strange behavior of the horizontal scroll bar. I am completely satisfied with the result.

Since these changes made by the patch are not necessary for most programmers, except for those who are dealing with microcontrollers, the topic is closed.
 
All health and good luck.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #37 on: March 17, 2021, 06:19:25 pm »
Oh, I see now, github have made it that you have to submit the review, so you've not seen my comments. Now you have to be able to see them.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #38 on: March 18, 2021, 03:32:25 pm »
Now you have to be able to see them.
I have read them and will make your changes to the latest version with wxListBox in a new pull request. Since I have made many additions related to wxListBox, you will need to check them again.



Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13338
    • Travis build status
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #39 on: March 18, 2021, 04:37:10 pm »
If you open another pull request, I'll just close it without looking at it. Lets finish this one first.
If you want to introduce more changes introduce them in this pull request.

Keep in mind that I think the API around the examine memory feature is incorrect/bad/unoptimal and it should be adjusted.
I have ideas, but no time, as always, so it is what it is.
But spending time around it is not really worth it that much.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #40 on: March 18, 2021, 06:38:15 pm »
Ok I'll make the necessary changes to this request, the debugger needs rework. Some of the code in the program hasn't changed for over 5 years, but there are a lot of new plugins.

Offline MicroSourceCode

  • Multiple posting newcomer
  • *
  • Posts: 23
Re: Patch for codeblocks 20.03 adding multi columns in memory dump
« Reply #41 on: March 19, 2021, 06:17:39 pm »
I was unable to make changes to the existing pull request because I foolishly deleted
fork of the program. I am new to github. After some thought, I came to the conclusion that this is even good, since my changes in the patch are closely related to the existing debugger, and since the debugger, as I understand it, will be redone this year, there is no point improve the code that will stop working. I'll wait for the changes in the debugger ...