Jump to content

P4 C++ Api 18.2 bug: Memory stomp!

C++ bug

  • Please log in to reply
No replies to this topic

#1 Zerman



  • Members
  • Pip
  • 1 posts

Posted 07 May 2020 - 04:16 AM

Recently I'm working on itegrating P4 to my game editor. However I found my editor is not stable now, one struct is always corrupted. After debugging with data breakpoints, I found the call stack below:

> vcruntime140.dll!memcpy()
  EditorDev.exe!StrBuf::Append(const char * buf) line 450 C++
  EditorDev.exe!StrBuf::Set(const char *) line 417 C++
  EditorDev.exe!GetCwd(StrBuf * dest, int charset) line 142 C++
  EditorDev.exe!HostEnv::GetCwd(StrBuf & result, Enviro * enviro) line 184 C++
  EditorDev.exe!Client::GetCwd() line 154 C++
  EditorDev.exe!Client::SetTrans(int output, int content, int fnames, int dialog) line 75 C++
  EditorDev.exe!Client::LateUnicodeSetup(const char * value, Error * e) line 560 C++
  EditorDev.exe!Client::SetupUnicode(Error *) line 526 C++
  EditorDev.exe!Client::Init(Error * e) line 132 C++

It seems this memcpy is out-of-bound. Have the dev team already known this bug?

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users