Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix #11646: Non-thread safe shared buffer returned from GetLogPrefix(). #11648

Merged
merged 1 commit into from Jan 18, 2024

Conversation

PeterN
Copy link
Member

@PeterN PeterN commented Dec 30, 2023

Motivation / Problem

GetLogPrefix reuses a static std::string, and returns its buffer after updating it. This is not thread safe.

This is probably a left-over from using C-style strings.

Description

Return string from GetLogPrefix instead of shared string's buffer.

Limitations

Checklist for review

Some things are not automated, and forgotten often. This list is a reminder for the reviewers.

  • The bug fix is important enough to be backported? (label: 'backport requested')
  • This PR touches english.txt or translations? Check the guidelines
  • This PR affects the save game format? (label 'savegame upgrade')
  • This PR affects the GS/AI API? (label 'needs review: Script API')
    • ai_changelog.hpp, game_changelog.hpp need updating.
    • The compatibility wrappers (compat_*.nut) need updating.
  • This PR affects the NewGRF API? (label 'needs review: NewGRF')

src/debug.cpp Outdated Show resolved Hide resolved
glx22
glx22 previously approved these changes Dec 30, 2023
@glx22 glx22 dismissed their stale review December 30, 2023 00:28

Missed outdated comment

src/console.cpp Outdated Show resolved Hide resolved
…Prefix().

Return string from GetLogPrefix instead of shared string's buffer.
@rubidium42 rubidium42 merged commit 28ef514 into OpenTTD:master Jan 18, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants