gabime / gabime/spdlog

inline registry leads to split instances across .so borders

Open
#3,003 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
29.6k
Forks
5.4k
Avg merge
4d 21h
Merged PRs (30d)
3

Description

SPDLOG_INLINE registry &registry::instance() returns local instance in each so, preventing configuration and central reuse of logger.

sample naive configuration, with most(all?) default spdlog build/use possibilities not achieving expectations:
+main exe
+shared/reused common libs(static/dynamic)
+multiple plugins .so
all using (expected to be same?) logger

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing SPDLOG_INLINE registry::instance() and reproduce the configuration across the main executable, shared or static common libraries, and multiple plugins described in the issue. Determine whether one logger instance across .so boundaries is supported and define the expected behavior before identifying the affected implementation and validation needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
observability-sre
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.