You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: