Google is committed to advancing racial equity for Black communities. See how.

fx symbolize

symbolize backtraces and program locations provided as input on stdin

usage: fx symbolize [--experimental] [--legacy] [-i IDS_TXT_FILE]
                    [-r | --remote-symbols]

   --experimental          use the experimental C++ symbolizer

   --legacy                use the legacy Go symbolizer

   -i IDS_TXT_FILE         specify an ids.txt file to be used

   --remote-symbols|-r     attemp to resolve symbols using predefined remote
                           symbol servers for symbols that cannot be resolved

   --auth                  (C++ symbolizer) start the authentication process.

  Converts sybmolizer markup found in stdin to human readable using
  local symbols (and remote if the --remote-symbols option is used).
  This command is usually used on log output from either zx_log or syslog.
  Anything that is not valid symbolizer markup is left alone. This is similar
  to how c++filt works for demangling C++ symbols.

  By default, `fx log` and `fx klog` automatically pipe their results into
  this command.

  --experimental / --legacy controls which implementation to use. The default
  is to use the experimental symbolizer.


  If the `--remote-symbols` option is specified, authentication for the symbol
  server is needed.

  When using the Go symbolizer, `fx symbolize` will fail if the current user
  is not authenticated or doesn't have enough privileges on the symbol
  servers. To ensure that the current user is properly authenticated, run:
     `gcloud auth application-default login`

  When using the C++ implementation, failed or missing authentication will be
  silent. To authenticate, run:
     `fx symbolize --experimental --auth`

symbolize source code