Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-docs gst-docs
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 57
    • Issues 57
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-docsgst-docs
  • Issues
  • #3

Closed
Open
Created Sep 18, 2013 by Bugzilla Migration User@bugzilla-migration

Document debug levels and debugging techniques

Submitted by pio..@..sf.net

Link to original bug (#708331)

Description

first off, is there any difference between the environment var GST_DEBUG and the commandline-option --gst-debug? if not then this should be mentioned. but the major issue here is that man-page merely mentions the possibility to increase debug level, and suggests to use --gst-debug-help to get more info. this way that option gets too little emphasis, which is strange for a tool that's supposed to be merely a sandbox for testing out pipelines. there certainly are parts that can be debugged and that do not depend on whatever external plugins. please make a choice of the most useful debug options and put them into the man-page with the GST_DEBUG or --gst-debug info. it's good to see some examples for gst-launch usage, but for a programmer more interesting would be to also see examples for how to learn more about what is happening under the hood. maybe also a section called troubleshooting could be added. there frequently asked questions could be addressed with some fitting debug-levels. in other words, please put more emphasis on the possibility of debugging within the man-page. at least to me, now that I know of this possibility, gst isn't as frightening a beast as it was before...

Assignee
Assign to
Time tracking