A pointer is just a variable such as any other one (an integer or a double, etc).
Therefore there is no such a thing such as "an invalid pointer", as you say, exactly as there is no such a thing as "an invalid variable"!!! That said, with a very good faith, I take that you meant "a pointer to invalid memory". An attempt to free an invalid portion of memory is equivalent to an attempt to free memory that has not been allocated. The point here is that the free() operation cannot be completed successfully. 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! Also remember the comments are for developers only and developers have their right to comment in whatever *style* they prefer, as long as correct and unambiguous information is provided. Of course, you can still submit your own patch, if you like, to modify comments from other developers... Guido Il 15 novembre 2018 22:15:48 CET, "Stefan Brüns" <stefan.bru...@rwth-aachen.de> ha scritto: >On Donnerstag, 15. November 2018 22:11:02 CET Guido Trentalancia wrote: >> Yes, that is equivalent to a double free operation, i.e. an attempt >to free >> memory that has not been previously allocated. > >A double free is calling free twice on the same valid! pointer. > >"or corruption" is the case here, tmp is an invalid pointer. > > >-- >Stefan Brüns / Bergstraße 21 / 52062 Aachen >home: +49 241 53809034 mobile: +49 151 50412019 > >------------------------------------------------------------------------ > > > >------------------------------------------------------------------------ > >_______________________________________________ >sigrok-devel mailing list >sigrok-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/sigrok-devel
_______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
