Joined October 2015
- Tweets 2,859
- Following 318
- Followers 1,345
- Likes 1,078
1,320 Photos and videos
Jun 13
It's time for our weekly weekend challenge: find the bug with PVS-Studio! Today, your challenge is to spot the error from S&Box project.
Wanna answer? Grab it here: pvs-studio.com/en/blog/posts…
#Csharp #Dotnet #Gamedev #Debugging
4
247
Jun 12
Behold! A new thread with PVS-Studio findings. A while back, we analyzed a bunch of open-source projects for EAP, and one of them was Visual Studio Code.
What do you see here?
V7001 The operands of the '===' operator are equivalent.
#NodeJS #JS #Development #Programming #JavaScript
1
3
397
Jun 12
We've shown you what we found using our tool, and we believe developers will fix it (or have already done so). This is just a tiny error from the world of the JS projects.
Learn more: pvs-studio.com/en/blog/posts…
1
88
Jun 12
You can also try the analyzer on your own projects.
Join the beta testing and check your code using PVS-Studio:
pvs-studio.com/en/pvs-studio…
59
Jun 12
We’ve hosted webinars, and our experts have appeared as guests at well-known industry conferences and podcasts.
Now, we’d like to try something new: our very own podcast! And we need YOU as a guest.
Our podcast is less about idle talk, more deep tech discussions. If you’re passionate about tech and would like to talk about engineering, development, tools, languages, architecture, industry trends, or even the challenges behind building real-world software, we’d be glad to have you on board.
Yuri Minaev is a C static analyzer architect at PVS-Studio and an experienced C developer, a recognizable voice in the C community.
Interested? Drop a comment or send us a DM who are you and what do you want to discuss, and we'll contact you.
Thank you!
#Cpp #Java #Csharp #Development #Developers #Podcast
122
Jun 11
We brought some useful info for you from our last webinar!
Full video: youtube.com/watch?v=yFz1LTtE…
Next webinar: pvs-studio.com/en/webinar/
#Cpp #Tokenization #Lexer #ProgrammingLanguage
1
185
Jun 10
The PVS-Studio team keeps on adding new diagnostic rules to the Go analyzer. Today, we show how V8013 works.
In Go, you can explicitly pick which argument a placeholder uses. If you explicitly specify that the` n` argument should be substituted, the `n 1` argument will be used next.
In the example, ` %[1]s` uses `tableName` and implicitly shifts the argument index for the next placeholder by 1. So, the next placeholder uses `constraint`, not the intended `err`.
1
1
1
311
Jun 10
Want to be part of the Go analyzer beta testing? We'll be glad to see you: pvs-studio.com/en/pvs-studio…
205
Jun 9
A few words from our speaker on the upcoming session:
'Let's make a programming language. AST'.
Join here: pvs-studio.com/en/webinar/30…
2
295
Recent PVS-Studio checks in CMake’s nightly CI identified:
• Unguarded dereferencing
• Possible out-of-bounds errors
• Unsafe buffer manipulation
• Raw pointer inserted into a container without ownership safety
These issues often remain hidden until later code changes or unexpected internal states make them observable.
Read more: ow.ly/6VnK50Z4aGU
#CMake #PVSStudio #CItools
1
3
459
PVS-Studio retweeted
Jun 4
Miranda IM and dozens of other open source projects had this exact bug
PVS Studio found it in more than 100 real codebases
what is the output when s = "" (empty string)?
35
8
83
13,787
Jun 6
What the lexer functions can do? Watch in the short video.
Full video: youtube.com/watch?v=yFz1LTtE…
Next webinar: pvs-studio.com/en/webinar/
#Cpp #Tokenization #Lexer #ProgrammingLanguage
2
367
Jun 6
Our tool found that. Give a try to yourself and find the error in the Jetty project.
Answer here: pvs-studio.com/en/blog/posts…
#Java #Programming #PVS_Task #Debugging
1
4
256
Jun 5
As usual, we'll show you the code (today, it'd be the Golang code) and explain what bugs it has contained inside. It has been detected by the PVS-Studio diagnostic rule V8015 Suspicious use of the bitwise XOR operator '^'. The exponentiation operation may have been intended here.
1
3
331
Jun 5
The 'BitSet' length will be much smaller than expected due to initialization performed by 'bitset.New'. As a result, the program will spend time extending the length and recopying data in the 'Set' method via 'extendSet'. It could be avoided if the 'BitSet' were initialized with the correct length from the start.
1
150
Jun 5
We’ve found other bugs detected by our analyzer and and by now the bug may have already been fixed. If you have any thoughts, we’d be glad to discuss them!
You can explore other finding here.
pvs-studio.com/en/blog/posts…
138