This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/op25-dev@lists.osmocom.org/.
Matt D md123 at nycap.rr.comOn 08/08/2013 03:56 AM, Steve Glass wrote: > Ok, so its telling you that there is a bad pointer being passed to > free. Things you can do: * Set "ulimit -c unlimited" in the shell > before running the program. That way you get a "core" file when the > program crashes and can run the debugger on it to find out why. * > Run valgrind on the executable. When the program finishes it will > produce a summary of all memory errors. Hope that helps. Stevie > Hey, Thanks. So I am running op25 with valgrind. i saw a lot of complaints while op25 started and it is running now. it may take some time, maybe hours or maybe days, for op25 to die with this memory problem. so i should wait for it to die right? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20130808/259c01fa/attachment.htm>