Forum > Debugger

Mysterious Debugger message

<< < (2/2)

winni:
Hi!

Thanx for all the hints.

I enabled the heaptrace which showed me an awfull amount of unfreed memory.

Following the heaptrace messages and your hints about dangling pointers I found the "evil":

A pBGRApixel (Pointer to pixel) outside the  dimensions of a BGRAbitmap.

Thanx to everybody.
Problem solved and something learned about (late) strange behaviour.

Winni

Martin_fr:
After a crash, heaptrc is likely to report a lot. After all, the crash terminates your app before it gets to free the mem.

About the "outside access" => Valgrind is really good at finding those. Even if they do not cause an error.

winni:

--- Quote from: Martin_fr on September 17, 2021, 03:07:22 pm ---After a crash, heaptrc is likely to report a lot. After all, the crash terminates your app before it gets to free the mem.

About the "outside access" => Valgrind is really good at finding those. Even if they do not cause an error.

--- End quote ---

Hi!

Yes I know. But  anyway heaptrace gave me the necessary infos.
I know about valgrind.  But it is not easy to read .....

Winni

Martin_fr:

--- Quote from: winni on September 17, 2021, 03:58:35 pm ---Yes I know. But  anyway heaptrace gave me the necessary infos.
I know about valgrind.  But it is not easy to read .....

--- End quote ---

Menu: View > Leaks and traces

You can import the valgrind output (at least for the memcheck tool)

Navigation

[0] Message Index

[*] Previous page

Go to full version