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

Use AddressSanitizer before posting crash issues #1757

Closed
uNetworkingAB opened this issue Jun 22, 2024 · 0 comments
Closed

Use AddressSanitizer before posting crash issues #1757

uNetworkingAB opened this issue Jun 22, 2024 · 0 comments

Comments

@uNetworkingAB
Copy link
Contributor

No human person on this planet can write bug free C++ without using AddressSanitizer or Valgrind religiously. If you don't use these tools, your code is, by definition, entirely broken even if it just happens to work [even in] in production.

Don't post bug reports such as "look at this, my app crashes". In 99 out of 100 bug reports, the bug is in your app and your ill-use of C++ (which is an anything-goes language).

Having a crash where the stack trace shows the fault originated from uWS source code means nothing. Any ill-use of threading or memory corruption can manifest like this. You really only know if you use AddressSanitizer to check for the first mistake.

Using these tools will make you a better developer writing better code and be more aware of what is legal and illegal use of the language.

@uNetworkingAB uNetworkingAB pinned this issue Jun 22, 2024
@uNetworking uNetworking locked as resolved and limited conversation to collaborators Jun 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant