Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

Are there any specific configurations needed to enable debug lines from util-linux? Also what message channel are they sent? E.g., logfile, syslog, etc. I think these things should be added in the README.

Tips on how to insert new debug lines would be helpful too. This saves the debugger's time.

You must be logged in to vote

Replies: 2 comments · 1 reply

Comment options

Well, util-linux is a large set of tools with different use cases. I do not think there is a generic answer.

  • shared libraries usually use LIBxxxx_DEBUG=all env. variable to print debug messages on stderr (e.g. LIBMOUNT_DEBUG=all findmnt).
  • debugger stuff can be enabled by adding -g to CFLAGS, for example, by CFLAGS="-g" ./configure
  • some tools provide verbose output, for example, hardlink
  • some tools need code modification (e.g. agetty)
You must be logged in to vote
0 replies
Comment options

Maybe a more specific question: how does one get the DBG() code in https://github.com/util-linux/util-linux/blob/master/lib/fileeq.c#L510-L555 to execute for example?

You must be logged in to vote
1 reply
@karelzak
Comment options

ULFILEEQ_DEBUG=all hardlink ...

I have added a note about this env. variable to the hardlink man page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
🙏
Q&A
Labels
None yet
3 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.