To get a trial key
fill out the form below
Team License (standard version)
Enterprise License (extended version)
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

** This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
Examples of errors detected by the V541…

Examples of errors detected by the V541 diagnostic

Apr 05 2021

V541. It is dangerous to print a string into itself.


PCSX2

V541 It is dangerous to print the string 'fileData' into itself. pcsx2 patchbrowser.cpp 211


void ListPatches (HWND hW) {
  ....
  while((tmpi=fgetc(fp)) != EOF)
    sprintf(fileData,"%s%c",fileData,tmpi);
  ....
  sprintf(tmpStr,"%s (%s)",tmpStr,FindData.cFileName);
  ....
}

The code might work, but this is a dangerous game.

Similar errors can be found in some other places:

  • V541 It is dangerous to print the string 'tmpStr' into itself. pcsx2 patchbrowser.cpp 239

CAMEL

V541 It is dangerous to print the string 'szOperatingSystem' into itself. stickies camel.cpp 572


char * OSDetection ()
{
  ....
  sprintf (szOperatingSystem, "%sversion %d.%d %s (Build %d)",
           szOperatingSystem,
           osvi.dwMajorVersion,
           osvi.dwMinorVersion,
           osvi.szCSDVersion,
           osvi.dwBuildNumber & 0xFFFF);
  ....
  sprintf (szOperatingSystem, "%s%s(Build %d)",
           szOperatingSystem, osvi.szCSDVersion,
           osvi.dwBuildNumber & 0xFFFF);
  ....
}

The code might work, but this is a dangerous game.

Similar errors can be found in some other places:

  • V541 It is dangerous to print the string 'szOperatingSystem' into itself. stickies camel.cpp 603

Mozilla Firefox

V541 It is dangerous to print the string 'newhost' into itself. ssltunnel.cpp 531


bool AdjustWebSocketHost(relayBuffer& buffer,
                         connection_info_t *ci)
{
  ....
  sprintf(newhost, "%s:%d", newhost,
          PR_ntohs(inet_addr.inet.port));
  ....
}

The code might work, but this is a dangerous game.


UCSniff

V541 It is dangerous to print the string 'dst' into itself. vc_format.c 177


int hex_format(...., u_char *dst)
{
  ....
  sprintf(dst, "%s %04x: ", dst, i );
  ....
}

The code might work, but this is a dangerous game.

Similar errors can be found in some other places:

  • V541 It is dangerous to print the string 'dst' into itself. vc_format.c 183
  • V541 It is dangerous to print the string 'dst' into itself. vc_format.c 185
  • V541 It is dangerous to print the string 'dst' into itself. vc_format.c 200

TinyCAD

V541 It is dangerous to print the string 'csText' into itself. childfrm.cpp 79


void CChildFrame::OnUpdateFrameTitle(BOOL bAddToTitle)
{
  ....
  CString csText;
  ....
  if (m_nWindow > 0)
    csText.Format(_T("%s: %d"), csText, m_nWindow);
  ....
}

Scilab

V541 It is dangerous to print the string 'lines' into itself. sci_toprint.cpp 314


static int sci_toprint_two_rhs(void* _pvCtx,
                               const char *fname)
{
  ....
  sprintf(lines, "%s%s\n", lines, pStVarOne[i]);
  ....
}

Similar errors can be found in some other places:

  • V541 It is dangerous to print the string 'coserr.buf' into itself. sci_coserror.c 94

FreeBSD Kernel

V541 It is dangerous to print the string 'buffer' into itself. ata-highpoint.c 102


static int
ata_highpoint_probe(device_t dev)
{
  ....
  char buffer[64];
  ....
  strcpy(buffer, "HighPoint ");
  strcat(buffer, idx->text);
  if (idx->cfg1 == HPT_374) {
  if (pci_get_function(dev) == 0)
      strcat(buffer, " (channel 0+1)");
  if (pci_get_function(dev) == 1)
      strcat(buffer, " (channel 2+3)");
  }
  sprintf(buffer, "%s %s controller",
    buffer, ata_mode2str(idx->max_dma));
  ....
}

Similar errors can be found in some other places:

  • V541 It is dangerous to print the string 'buffer' into itself. ata-promise.c 208

Serious Engine 1 v.1.10

V541 It is dangerous to print the string 'achrDefaultScript' into itself. dlgcreateanimatedtexture.cpp 359


BOOL CDlgCreateAnimatedTexture::OnInitDialog()
{
  ....
  // allocate 16k for script
  char achrDefaultScript[ 16384];
  // default script into edit control
  sprintf( achrDefaultScript, ....); // <=
  ....
  // add finishing part of script
  sprintf( achrDefaultScript,        // <=
           "%sANIM_END\r\nEND\r\n",  // <=
           achrDefaultScript);       // <=
  ....
}

Ardour

V541 It is dangerous to print the 'buf' string into itself. luawindow.cc 490


void
LuaWindow::save_script ()
{
  ....
  do {
    char buf[80];
    time_t t = time(0);
    struct tm * timeinfo = localtime (&t);
    strftime (buf, sizeof(buf), "%s%d", timeinfo);
    sprintf (buf, "%s%ld", buf, random ());
  ....
}

Popular related articles
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…

Comments (0)

Next comments

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →
Accept