Re: free(): double free detected in tcache 2

Denis Corbin <[email protected]> Thu, 27 Feb 2020 19:49:13 +0100
Newsgroups	gmane.comp.sysutils.backup.dar.support
Message-ID	<[email protected]>

On 27/02/2020 18:46, Graham Cobb wrote:
>>
>> yep, this code has not changed for years... The problem occurs at etage
>> object construction. Its field "fichier" should be initalized by default
>> before the etage constructor code is ran. The first thing that is done
>> is to invoke the std::deque::clear() method on this one, which seems to
>> be the #5 in the stack.
> 
> It looks like this may be a debian packaging bug... I have just realised
> that when I upgraded dar to 2.6.8, it did not upgrade libdar to 2.6.8 as
> well. So, I have been running with dar 2.6.8 but libdar 2.6.6.

what is strange is that from 2.6.6 to 2.6.8 the dar binary only changed
by a few comments (copyright date) nothing changed in the way dar calls
libdar.

On the other side, libdar API has not changed at all between those
release only bug fixes took place inside libdar.

Normally, the dar of 2.6.8 could rely libdar from 2.6.6 and 2.6.7 the
same as libdar from 2.6.8.

> 
> I have now upgraded libdar to 2.6.8 as well and the backup is now
> running. I will provide another reply when it finishes to let you know
> if it is successful.

If Debian maintainer wants to have dar 2.6.8 working with libdar 2.6.6
I have no objection even if it has not much use, it should work. Though
there may be some problem/some difference in the way dar/libdar have
been compiled from 2.6.6 to 2.6.8 (?)

> 
> If so, I will report a debian bug saying that dar should have a
> dependency on the same version of libdar. Is that correct?
> 

Well the only dependency that is mandatory and (dar will test it at
initialization time) is that the libdar major version must be the same
as the one dar has been linked with at compilation time, medium version
should be greater or equal to the one used at compilation time and minor
version is free, though the highest, the better as it provides bug
fixes, new feature are very rare and only if this is completely
independent of the rest like the python interface added recently.

So it makes sense to have libdar upgraded with dar to benefit from the
bug fixes (dar by itself is really just a CLI to API translation and it
does not change often, at the opposite of libdar).

> 

Anyway, thank you for your feedback and you should now be good to
perform and test your backup efficiently

Regards,
Denis

_______________________________________________
Dar-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dar-support
signature.asc (application/pgp-signature, 833 B)