Author Topic: CC log many messages as NativeParser::SafeExecute: Re-Entry protection  (Read 411 times)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5226
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Code: [Select]
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::GetCompilerUsingStandardGCC: Using language standard: -std=gnu++11
NativeParser::SafeExecute: Re-Entry protection.
NativeParser::DoFullParsing: AddCompilerPredefinedMacros failed!
NativeParser::DoFullParsing: Adding cpp/c files to batch-parser
NativeParser::DoFullParsing: Added 461 source file(s) for project 'Code::Blocks wx3.1.x' to batch-parser...


This is using the latest svn build myself when opening the C::B project.
Any ideas how those are happened?  :)

I think this log message were added my morten's recent commit: (rev 11782)
Code: [Select]
* CC: Fixed annoying bug that the compiler calls fail due to missing dependencies (DLLs) and crashes. This happened esp. is projects with multiple targets that use different compilers like MinGW32 and MinGW64. Now, all compiler calls (i.e. for macros, constants...) are safely executed by temporarily expanding the PATH variable such that the compiler can find the right libraries. Also, it is safe-guarded against re-entry for threaded calls. Most experienced on Windows. Might not have been an issue on Linux at all.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.