> On 9 Mar 2026, at 14:07, Ranier Vilela <[email protected]> wrote:
> Coverity has some alerts about the function *RestoreArchive*, > arguing that there are null variable dereferences. Coverity is very good at generating false positives. > I haven't done in-depth research to determine if this is correct or not. > However, the code can be simplified to a single check that would silence > notifications and protect against this issue. You probably should do that research. What if te is actually null and with your patch the code accepts it rather than crashes. Does that affect the integrity of the dump? Will it crash soon after? Is te allowed to be null? -- Daniel Gustafsson
