Author Topic: memory detecting tool embeded in Code::Blocks for Windows, create a new plugin?  (Read 3943 times)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6034
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Hi, we already have a plugin named "Valgrind plugin", see some images here: How to use valgrind in code::blocks?

But Valgrind plugin is mainly for Linux. I see a similar tool under Windows, named "heob", see here: heob

QTCreator has already embeded this tool, see here: Profiling and Memory Checking Tools - Qt Wiki and Heob | Qt Creator Documentation

So, what I need to do is: copy the code of Valgrind plugin, and modify the code to support heob tool.

Any good ideas? 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 eckard_klotz

  • Almost regular
  • **
  • Posts: 201
Hello Ollydbg.

Do you know if somebody has already collected some experiences with using Dr. Memoryhttps://drmemory.org/index.html together with Code::Blocks?

Best regards,
                   Eckard Klotz.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 6034
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Hello Ollydbg.

Do you know if somebody has already collected some experiences with using Dr. Memoryhttps://drmemory.org/index.html together with Code::Blocks?

Best regards,
                   Eckard Klotz.

Thanks. I know Dr. Memory is a good tool, I haven't used it recently. Anyone has some experience can show your result here.

When I use the heob, I see it is hard to read its result diagram, see discussion here:

https://github.com/ssbssa/heob/issues/32#issuecomment-2314412319
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.