On Tue, Sep 8, 2015 at 12:28 AM, scan-admin@coverity.com wrote:
1614 case TWO(STRING_ALLOC_SUBSTRING,1): 1615 Pike_fatal("This should not happen, substrings are never unlinked.\n");
CID 1323178: Control flow issues (MISSING_BREAK) The above case falls through to this one.
1616 default:
Shouldn't Pike_fatal be marked as a non-returning function?
ChrisA
It is. I haven't been able make Coverity to take the correct action with that information.
/Peter Bortas On 7 Sep 2015 16:31, "Chris Angelico" rosuav@gmail.com wrote:
On Tue, Sep 8, 2015 at 12:28 AM, scan-admin@coverity.com wrote:
1614 case TWO(STRING_ALLOC_SUBSTRING,1): 1615 Pike_fatal("This should not happen, substrings are never
unlinked.\n");
CID 1323178: Control flow issues (MISSING_BREAK) The above case falls through to this one.
1616 default:
Shouldn't Pike_fatal be marked as a non-returning function?
ChrisA
pike-devel@lists.lysator.liu.se