Skip to content

Arbitrated client stucks -> dead lock #171

@SASIDHARAN-dot

Description

@SASIDHARAN-dot

Why the kErpcStatus_Timeout check is needed for releasing the semaphore in case of any error during erpc call in TransportArbitrator::receive() function? Because I don't see any function returning kErpcStatus_Timeout value. This check needs to be reverted and should release the semaphore for any erpc related errors.

Metadata

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