Add ability to log allocations/frees for easily reporting bugs #8
Labels
Comments
|
I'm reading the source code more carefully to see if I can give this one a crack! |
|
@joaolucasl Awesome -- let me know if you have any questions! |
|
hi @fitzgen I would like to try this one. I don't know if this lib is still mantained and actively updated. Or there are any alternatives that made this lib obsolete. But if this lib is still up to date and you're mantaining it, I would like to help! And also learn, why not 😅 I'm not sure whether @joaolucasl is still developing this. But I guess not. So if it's ok for you @fitzgen I'll give it a try! |
|
Go ahead @CPerezz, I tried at the time and after a while trying I just left it alone. If you want, feel free to give it a crack |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
We would write all allocations and frees into a buffer that we periodically flush to a file. When people report a bug, they could enable this feature, and provide their log.
Motivation
Easier to file bugs. Easier to reproduce bugs. Therefore, easier to fix bugs.
Details
Behind a cargo feature.
I guess we could use
std::io::BufWriter, and say that this feature requiresstdIdeally this would use the same operation definitions in
./test, so we could trivially turn them into regression tests. Also, shrink them to get reduced test cases.The text was updated successfully, but these errors were encountered: