[Bug 2151756] Re: Stack traces show line numbers without any source reference

[Marco Trevisan (Treviño)]

** Description changed:

  [ Impact ]
  
  When a Stack Trace is created by the retrace service we do show the line
  numbers, but even if the source is available it may not contain any
  version information, making it very hard to figure out what we are
  really debugging.
  
  The reports may contain a "StacktraceSource" field, but this is not
  filled for multi-thread operations nor exposed in errors.ubuntu.com in
  the right way.
  
  [ Test case ]
  
  Given a crash file:
-  - apport-retrace binary.crash
+ $ apport-retrace binary.crash
  
  After this, inspect the crash file (using apport-unpack, or apport-cli
  -> View)
  
  The file should contain the `Stacktrace` and `ThreadStacktrace` fields
  that include the file being called.
  
  For example:
  
  $ sudo apt install chaos-marmosets
  $ seg-fault
  $ sudo cp /var/crash/_usr_bin_seg-fault.$(id -u).crash /tmp
  $ sudo chown $USER /tmp/_usr_bin_seg-fault.$(id -u).crash
  $ apport-retrace /tmp/_usr_bin_seg-fault.$(id -u).crash
  $ apport-cli /tmp/_usr_bin_seg-fault.$(id -u).crash
  
  Select "[V]iew"
  
  The fields StacktraceSource, ThreadStacktrace and Stacktrace should all
  show the source line that caused the crash to happen
  
  [ Regression Potential ]
  
  As before the sources are always downloaded (if available) unless `--no-
  stacktrace-source` is passed, although now the source download happens
  before interacting with gdb.
  
  This does not imply much change a part the ordering, as even in case of
  download issues, we already were failing without either 1) using the
  sources or 2) raising without updating the crash report file.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2151756

Title:
  Stack traces show line numbers without any source reference

Status in apport package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  When a Stack Trace is created by the retrace service we do show the
  line numbers, but even if the source is available it may not contain
  any version information, making it very hard to figure out what we are
  really debugging.

  The reports may contain a "StacktraceSource" field, but this is not
  filled for multi-thread operations nor exposed in errors.ubuntu.com in
  the right way.

  [ Test case ]

  Given a crash file:
  $ apport-retrace binary.crash

  After this, inspect the crash file (using apport-unpack, or apport-cli
  -> View)

  The file should contain the `Stacktrace` and `ThreadStacktrace` fields
  that include the file being called.

  For example:

  $ sudo apt install chaos-marmosets
  $ seg-fault
  $ sudo cp /var/crash/_usr_bin_seg-fault.$(id -u).crash /tmp
  $ sudo chown $USER /tmp/_usr_bin_seg-fault.$(id -u).crash
  $ apport-retrace /tmp/_usr_bin_seg-fault.$(id -u).crash
  $ apport-cli /tmp/_usr_bin_seg-fault.$(id -u).crash

  Select "[V]iew"

  The fields StacktraceSource, ThreadStacktrace and Stacktrace should
  all show the source line that caused the crash to happen

  [ Regression Potential ]

  As before the sources are always downloaded (if available) unless
  `--no-stacktrace-source` is passed, although now the source download
  happens before interacting with gdb.

  This does not imply much change a part the ordering, as even in case
  of download issues, we already were failing without either 1) using
  the sources or 2) raising without updating the crash report file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2151756/+subscriptions