Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • YARR YARR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 68
    • Issues 68
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • YARR
  • YARRYARR
  • Issues
  • #80
Closed
Open
Created Sep 21, 2020 by Alex Toldaiev@otoldaie

Clear the `cout` from the debug messages in `libNetioHW` and implement proper logging?

Quite a few debug messages are printed to cout. In comparison, it seems libEmu prints to cout only in few cases, when it calls some doDump method or in some exceptions.

In order to cooperate well with powertools and OPC infrastructure, the cout should not contain the debug messages. I will make the corresponding PR, just need to know how the debug logs are implemented in YARR. Should I just direct them to cerr or use some logging system? For example, libEmu uses logging::make_log.

Assignee
Assign to
Time tracking