Please provide complete information as applicable to your setup.
**• Hardware Platform (Jetson / GPU)：jetson
**• DeepStream Version: 5.0
**• JetPack Version (valid for Jetson only): 4.4
**• TensorRT Version:7.1.3.0
Hi all,
I am custom my own plugin and want to output some log information.
In parse bbox function, I can use std::cout, nvds_log, printf and GST_INFO to output infomation.
But in my NvDsInferCudaEngineGet and NcDsInferInitializeInputLayers, none of above can get output. I have define "engine-create-func-name" in files and use --get-debug in command lines.
Any help?
Hi,
You need to change GStreamer debug level with the GST_DEBUG environment variable:
| # | Name | Description |
|---|---------|----------------------------------------------------------------|
| 0 | none | No debug information is output. |
| 1 | ERROR | Logs all fatal errors. These are errors that do not allow the |
| | | core or elements to perform the requested action. The |
| | | application can still recover if programmed to handle the |
| | | conditions that triggered the error. |
| 2 | WARNING | Logs all warnings. Typically these are non-fatal, but |
| | | user-visible problems are expected to happen. |
| 3 | FIXME | Logs all "fixme" messages. Those typically that a codepath that|
| | | is known to be incomplete has been triggered. It may work in |
| | | most cases, but may cause problems in specific instances. |
| 4 | INFO | Logs all informational messages. These are typically used for |
| | | events in the system that only happen once, or are important |
| | | and rare enough to be logged at this level. |
| 5 | DEBUG | Logs all debug messages. These are general debug messages for |
| | | events that happen only a limited number of times during an |
| | | object's lifetime; these include setup, teardown, change of |
| | | parameters, etc. |
| 6 | LOG | Logs all log messages. These are messages for events that |
| | | happen repeatedly during an object's lifetime; these include |
| | | streaming and steady-state conditions. This is used for log |
| | | messages that happen on every buffer in an element for example.|
| 7 | TRACE | Logs all trace messages. Those are message that happen very |
| | | very often. This is for example is each time the reference |
| | | count of a GstMiniObject, such as a GstBuffer or GstEvent, is |
| | | modified. |
| 9 | MEMDUMP | Logs all memory dump messages. This is the heaviest logging and|
| | | may include dumping the content of blocks of memory. |
You can filter the logs using your plugin name. For example, this will print all logs of elements that include video in the name:
GST_DEBUG=video*:6