On Thu, Nov 15, 2018 at 10:36:31PM +0100, Guido Trentalancia wrote: > But this seems just another meaningless and "out of theme" discussion, not > related to sigrok in any manner and which does not improve it, but rather > deteriorate it!
I just can't let the discussion end here. To me a double free is calling free twice on the same address where at the time of the first call there was a memory region starting at that address that was allocated with a function that returns memory to be deallocated with free (i.e. malloc, realloc, posix_memalign, etc.). If you call free on an address that was never allocated, it's not a double free. If you call free on an address that was allocated directly with mmap or brk, it's not a double free. If you call free on an address in the middle of a region allocated with malloc, it's not a double free. If you call free on a random address, the symptom might sometimes be a double free, but the error does not deserve to be called that way. Just my two cents Daniel _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
