We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tested with Valgrind, there are memory leaks coming from Lex. I ran 'das' with a simple file (4 instructions and one label).
LEAK SUMMARY: definitely lost: 0 bytes in 0 blocks indirectly lost: 0 bytes in 0 blocks possibly lost: 0 bytes in 0 blocks still reachable: 16,790 bytes in 4 blocks suppressed: 0 bytes in 0 blocks
The text was updated successfully, but these errors were encountered:
Welp thanks but I'm not actively working on das any more since 0x10c got canned :(
Sorry, something went wrong.
No branches or pull requests
Tested with Valgrind, there are memory leaks coming from Lex.
I ran 'das' with a simple file (4 instructions and one label).
LEAK SUMMARY:
definitely lost: 0 bytes in 0 blocks
indirectly lost: 0 bytes in 0 blocks
possibly lost: 0 bytes in 0 blocks
still reachable: 16,790 bytes in 4 blocks
suppressed: 0 bytes in 0 blocks
The text was updated successfully, but these errors were encountered: