bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 1/3] lib/regexec: Fix possible null-dereference


From: Paul Eggert
Subject: Re: [PATCH 1/3] lib/regexec: Fix possible null-dereference
Date: Wed, 11 Aug 2021 00:28:26 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0

On 6/18/21 8:44 AM, Darren Kenny wrote:
It appears to be possible that the mctx->state_log field may be NULL

How so? I don't see the execution path that would do that.

If you can see how it could happen, please let us know. Otherwise, does the attached patch pacify Coverity, and if not why not?

The DEBUG_ASSERT stuff does pacify GCC, as it tells GCC things that GCC isn't smart enough to figure out on its own. I hope Coverity can use similar advice.

Attachment: coverity.diff
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]