Skip to content

Option for compilation with ASan/MSan #393

@AshFungor

Description

@AshFungor

Hey, @riebl!

Do you think I's a good idea to add global option to enable sanitizers? I've been working in my fork for a while and had to use those at some point, but enabling them on per-target basis is a bit frustrating. Probably the best approach would be turning them on for all targets at once. The only issue I might think of is that only Artery modules would be tracked, Omnet++, INET and other external components would still be oblivious - though I don't think that debugging them should be considered here.

I'm also aware of available VS Code launch config for debugging, but to be honest I rarely tend to debug in such way, most of the time reports from sanitizers are more than enough to track memory issues and I use logging for everything else. So, what do you think?

Sorry, I'm quite busy at the moment, so I plan to get to work on Artery in December. Maybe someone could implement this earlier :)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions