Should C assertion failures have the "type-crash" label?

As part of triaging bugs found by the fuzzers, I’ve filed a number that involve C assertion failures. For example:

For bugs like these, should I be attaching the “type-crash” label on Github, or is that only for crashes impacting non-debug builds?

If a C assertion would fail in debug mode, chances are that you would get a crash later if in release mode. My vote would therefore be on attaching the “type-crash” label.

9 Likes

Agreed, they are crashes.

Sounds good. Thanks all.

Happy New Year!

2 Likes