Skip to content
New issue

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

missing try/catch for bad_alloc #30

Open
ronag opened this issue Apr 25, 2022 · 0 comments
Open

missing try/catch for bad_alloc #30

ronag opened this issue Apr 25, 2022 · 0 comments

Comments

@ronag
Copy link
Contributor

ronag commented Apr 25, 2022

Leveldb doesn't throw exceptions per se. But both the bindings and leveldb itself uses stl containers which uses allocators that throw bad_alloc. We should probably have a try/catch for each entry point catching bad allocs and returning the corresponding leveldb::Status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant