Yes, that is equivalent to a double free operation, i.e. an attempt to free memory that has not been previously allocated.
Therefore I believe the description is not ambigous or incorrect and this is proved and confirmed by the corresponding error quoted at the bottom. Guido Il 15 novembre 2018 22:02:44 CET, "Stefan Brüns" <stefan.bru...@rwth-aachen.de> ha scritto: >On Donnerstag, 15. November 2018 19:46:43 CET Guido Trentalancia wrote: >> Avoid double memory freeing leading to segmentation fault in >> the hameg-hmo driver when an SCPI command fails to get a >> string due conditions such as a timeout or an invalid command. >> >> # sr: scpi: Timed out waiting for SCPI response. >> # double free or corruption (!prev) > >While the change itself is correct, the commit message is wrong. In >case of an >error, tmp is left uninitialized and g_free is called with an invalid >argument. > >Regards, > >Stefan >-- >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
