Skip to content

🐛 __malloc_lock and __malloc_unlock are not resolved properly #16

@SizzinSeal

Description

@SizzinSeal

Expected Behavior

__malloc_lock and __malloc_unlock should be resolved to their definitions in src/system/mlock.c

Observed Behavior

__malloc_lock and __malloc_unlock are resolved to their definitions in libc.a

Additional Information

__malloc_lock and __malloc_unlock are used to prevent the scheduler preempting while a task is allocating memory. If this were to happen, memory corruption would be highly likely.

I don't know why libc has these definitions, per my knowledge they are supposed to be stubbed. Before we just strip these symbols from libc, we should figure out why they have strong definitions in libc just in case.

Prerequisites

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedother issues need to be resolved before this can be worked on

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions