Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C cmsgemos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 15
    • Merge requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cmsgemonline
  • gem-daq
  • cmsgemos
  • Issues
  • #103
Closed
Open
Created Aug 26, 2020 by Laurent Petre@lpetreOwner

Provide a stack-trace along with the exceptions in the RPC modules

Summary

Debugging any issue on the CTP7 is quite difficult due to the lack of the appropriate tools and the fact that it is remote system. In addition to a better logging, providing a stack-trace in the exceptions forwarded from the RPC modules to the DAQ machine would improve significantly the user experience.

What is the expected correct behavior?

A stack-trace is provided (or at least logged locally) for every exception thrown by a RPC method.

Assignee
Assign to
Time tracking