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

logging: add fvwm_debug infrastructure #79

Merged
merged 8 commits into from
May 27, 2020
Merged

logging: add fvwm_debug infrastructure #79

merged 8 commits into from
May 27, 2020

Conversation

ThomasAdam
Copy link
Member

@ThomasAdam ThomasAdam commented May 13, 2020

This adds a framework for handling fvwm_debug(), replacing the original fvwm_msg() calls.
Logging is now toggleable via SIGUSR2.

ThomasAdam and others added 7 commits May 26, 2020 00:03
For those systems which don't have asprintf natively, provide a
compatibility implementation.
Don't try and include more headers than is necessary by wrapping them in
an include guard.
Add log routines (modified from tmux) to be able to log what fvwm3 is
doing in a more structured way than just using fprintf() calls.
Move callers of asprintf() to xasprintf().
Make FVWM3 write or stop writing to a log file, when it receives
SIGUSR2.
This removes DBUG and associated configur.ac changes.

This will be replaced with more fuller logging.
@ThomasAdam ThomasAdam force-pushed the ta/logging branch 4 times, most recently from ae537db to 95fc6be Compare May 27, 2020 01:30
@ThomasAdam ThomasAdam self-assigned this May 27, 2020
@ThomasAdam ThomasAdam added this to the 1.0 milestone May 27, 2020
@ThomasAdam ThomasAdam linked an issue May 27, 2020 that may be closed by this pull request
@ThomasAdam ThomasAdam marked this pull request as ready for review May 27, 2020 01:32
Now that FVWM3 has logging capabilities via SIGUSR2, migrate all
instances of fprintf(stderr, ...) to fvwm_debug(...);

Although this might make the logfile chatty, it now means we won't miss
messages otherwise printed to stderr.  Some display managers (via
systemd) have started to make it harder to log/find stderr.

FVWM3 will create a log file in $HOME for the purposes of logging.
@ThomasAdam ThomasAdam changed the title logging: add log_debug infrastructure logging: add fvwm_debug infrastructure May 27, 2020
@ThomasAdam ThomasAdam merged commit 4a639a8 into master May 27, 2020
@ThomasAdam ThomasAdam deleted the ta/logging branch May 27, 2020 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Better logging required
1 participant