Skip to content

Assertions with cbor_assert(cond) #166

Open
@TSonono

Description

Hi,

I was wondering if there is a particular reason that the macro cbor_assert(cond) defined on line 64 in compilersupport_p.h is used instead of using a macro such as:

#  define MACRO do { if (!(cond)) return SomeCborError; } while (0)

The drawback of having an assertion from my point-of-view as someone who uses the library, is the fact that when the assertion fails, the program crashes. This is not ideal when I am fuzz testing my program since it will prevent me from knowing if it is my program that is causing the crash or the assertion from tinycbor.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions