So, for the first time since the previous report I've had to use dwarfsextract again.
I seem to keep running into some tricky files, cause once again I see garbage in console.
I'm not 100% percent sure if I nailed down the problem, but AFAICT it seems quite straightforward: in src/dwarfs/filesystem_extractor.cpp in close() you're calling check_result on the return of archive_write_free.
The catch is that check_result uses resources that archive_write_free will free, so the check (depending on timing) may give bogus results - for me that happens on every run (AFAICT).
So, for the first time since the previous report I've had to use dwarfsextract again. I seem to keep running into some tricky files, cause once again I see garbage in console.
I'm not 100% percent sure if I nailed down the problem, but AFAICT it seems quite straightforward: in
src/dwarfs/filesystem_extractor.cpp
inclose()
you're callingcheck_result
on the return ofarchive_write_free
. The catch is thatcheck_result
uses resources thatarchive_write_free
will free, so the check (depending on timing) may give bogus results - for me that happens on every run (AFAICT).