[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
debugging memory issues with asan?
I have been sloppy with my memory allocations and use in hte libcurses
testframe which, though the code seems to work, some tests fail when
jemalloc is enabled. I am trying to work out where to look but it is
difficult becuse there are lots of little memory allocations all over
the place. It was suggested to me to set MKSANITIZER=yes to try and
catch the errors. Sure enough, if I build the curses test frame with
MKSANITIZER=yes then the test process gets terminated and I get a memory
map dumped like this:
[blymn@rover] ./debug_test -v mvscanw
==15885==Shadow memory range interleaves with an existing memory
mapping. ASan cannot proceed correctly. ABORTING.
==15885==ASan shadow was supposed to be located in the
==15885==Process memory map follows:
.... and so on...
So, yes, I have a problem but I don't know where. How can I get more
information to help me find out where the issue is?
I am running a -current from around the end of April. I can update if I
really need to (I lag behind because this laptop is the machine I use
most so I like it stable...)
Sent from my NetBSD device.
"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
Main Index |
Thread Index |