Are you serious? I had `alias cl = clear` in my .bashrc file for so long that every time I ssh into a server I hit at least 3-4 "command not found" before getting used to typing the whole command... Of only I knew
@@emanuelescarsella3124 the first thing I do when connecting to a new server I'm managing : upload my .bashrc and .profile files (rhel seems to forget to make the .profile file that tells it to actually read the bashrc one)
Ctrl-L just clears the immediate buffer on a lot of terminals, while `clear` pretty consistently clears the entire buffer. Just a moderately annoying disclaimer for anyone.
As neat as this tool is, other existing tools like Coverity, cppcheck, or clang's static analyzer seem better suited and more mature for larger projects or modern C++.
I worked with the cavium sdk for a few days now, some old build, it would be hilarious to run this tool against any sdk by some large vendor, marvell, broadcast, citrix etc. (It would always end in tears, if you had to fix it)
Thanks bro. The switches are the stock switches that came with the rk royal kludge s98 keyboard, they call them "pale green switches". They are more clicky than the purple ones.
Well it highlights that the section of the code will not be executed under any conditions. Same would happen if you would write an IF condition that would never under any conditions be met.
My experience taught me to just use whatever is the best fit for the task at hand and don’t overcommit to any framework, language or os ✌️Me personally, I use all three, macos, ubuntu linux and windows.
I think you are missing the point of tools like this one. They are commonly used as part of the CI/CD pipeline as a gatekeeper to catch possible bad code in an automated way. Because while you might be using the debugger a lot of people don't.
@@EmiNNsoNify i guess but i still think everyone should use the debugger. that way everyone can be certain what their code is actually doing. automated tests like this will remain subject to the subjective valuations of the person who wrote the test. and if this person's values are wrong or produce terrible code, then everyone who abides by the test will then also produce terrible code
@@divinefavour1289Static analysis isn't an alternative to debugging though, they're meant to catch common mistakes and undefined behavior in a more objective way. Debugging also doesn't help in more complex projects until after you've spotted a bug; e.g. it's easy to miss a use-after-free issue that happens to work on one compiler/platform but not another. It's just not practical to manually debug every line of code in every possible configuration in large codebases; that's what static analysis, unit tests, and functional tests are meant for. If people are writing bad tests in your project, then they shouldn't pass code review in the first place otherwise you/the reviewers are also accountable.
CTRL-L will save you seconds of your life by not having to type clear.
TIL
another way : alias "c"="clear"
Are you serious? I had `alias cl = clear` in my .bashrc file for so long that every time I ssh into a server I hit at least 3-4 "command not found" before getting used to typing the whole command... Of only I knew
@@emanuelescarsella3124 the first thing I do when connecting to a new server I'm managing : upload my .bashrc and .profile files (rhel seems to forget to make the .profile file that tells it to actually read the bashrc one)
Ctrl-L just clears the immediate buffer on a lot of terminals, while `clear` pretty consistently clears the entire buffer. Just a moderately annoying disclaimer for anyone.
00:07 I work in security, I literally LOLd when you said “undisputed buffer overflow champion like you.” 😂
yes that is how jokes work, does not require imaginary security degrees ;)
As neat as this tool is, other existing tools like Coverity, cppcheck, or clang's static analyzer seem better suited and more mature for larger projects or modern C++.
I would also add codechecker and sonarlint to this list
ASan + Dr. Memory + Valgrind/Memcheck are the another tools for sanitizing the code.
I worked with the cavium sdk for a few days now, some old build, it would be hilarious to run this tool against any sdk by some large vendor, marvell, broadcast, citrix etc. (It would always end in tears, if you had to fix it)
Great video! What kind of switches are you using in that keyboard though? Sounds amazing.
Thanks bro. The switches are the stock switches that came with the rk royal kludge s98 keyboard, they call them "pale green switches". They are more clicky than the purple ones.
@@Tariq10x thank you!
It's true they make a pleasant sound.
Nice work! Thank you for the video.
undisputed buffer overflow champion like you! hahahahahahahhahahahahahahha nice one bro, i will use this.
1:12 this is why I have a job 😂
Lmao 😂
starfield?
Nobel prize buffer overflow
Why should i use this over GCC or Clang?
Is it like valgrind or something else
Valgrind execute the code.
"Cppcheck" is the static analyzer for C/C++.
No, it is more like cppcheck. It is static analysis, not runtime memory check like Valgrind.
It is based on Cousot & Cousot abstract interpretation. I was in the group that built it at NASA Ames, though it was a colleague’s project.
Nice keyboard.
Thx bro
"you write broken code and it's nothing new"
bro holds nothing back
Your keyboard takes most space of a screen! I guess it's too fancy to not show it
especially if its a friday afternoon 😭😭😭
If it is marking the rest of the code as dead, how is it a "static" code analyser?
Static means that it doesn't run the code itself
Well it highlights that the section of the code will not be executed under any conditions. Same would happen if you would write an IF condition that would never under any conditions be met.
This should exist for other languages too.
Static code analysis tools exist also for other languages ✌️
It does tho?? 😭😭
@@kowaihana yes
0_o Windows XP has a quite a few and the 1st I tried still works in Win 11 no way 😂
Rust to the rescue.
Fine ill go make an install script '-' why do you do these things
oko
VirtualBox instead of WSL2 or MinGW?
And?
No, WirtualBox.
No. Thanks 🖐
Can you elaborate?
Bunch of elitist haterrrrsss. I run win11 with wsl2 and raspberry pi os with some arch on the side. Windows #1😅
My experience taught me to just use whatever is the best fit for the task at hand and don’t overcommit to any framework, language or os ✌️Me personally, I use all three, macos, ubuntu linux and windows.
sorry man I have to dislike this video, because I saw Windows logo. I use arch btw
Understandable Sir, have a nice day.
@@Tariq10x same i have to dislike
use Rust
🙂
bro just use a debugger
I think you are missing the point of tools like this one. They are commonly used as part of the CI/CD pipeline as a gatekeeper to catch possible bad code in an automated way. Because while you might be using the debugger a lot of people don't.
@@EmiNNsoNify i guess but i still think everyone should use the debugger. that way everyone can be certain what their code is actually doing. automated tests like this will remain subject to the subjective valuations of the person who wrote the test. and if this person's values are wrong or produce terrible code, then everyone who abides by the test will then also produce terrible code
@@divinefavour1289regardless of what you think about debugging, there are use cases where attaching a debugger is not possible.
@@divinefavour1289Static analysis isn't an alternative to debugging though, they're meant to catch common mistakes and undefined behavior in a more objective way. Debugging also doesn't help in more complex projects until after you've spotted a bug; e.g. it's easy to miss a use-after-free issue that happens to work on one compiler/platform but not another.
It's just not practical to manually debug every line of code in every possible configuration in large codebases; that's what static analysis, unit tests, and functional tests are meant for. If people are writing bad tests in your project, then they shouldn't pass code review in the first place otherwise you/the reviewers are also accountable.
@@matts.1352 i see
Just use ChatGPT and AI😂🤣😂 Soon AI will replace programmers and make them completely obsolete💀☠
It is cool but nobody use C anymore
Yeah, nobody uses embedded systems and OS.
what a dimwit thing to say