Encourage users to get backtraces using apport

[Emmet Hikory]

On Dec 13, 2007 8:33 PM, Pedro Villavicencio Garrido <pedro at ubuntu.com> wrote:
> On Thu, 2007-12-13 at 10:08 +0100, Sebastien Bacher wrote:
> > "Missing a back trace
> >
> > Thank you for taking the time to report this bug and helping to make
> > Ubuntu better. Please try to obtain a backtrace following the
> > instructions at [WWW] http://wiki.ubuntu.com/DebuggingProgramCrash and
> > upload the backtrace (as an attachment) to the bug report. This will
> > greatly help us in tracking down your problem."
> >
> > Is that reply still required? It would make sense to use the "Missing a
> > crash report or having a .crash attachment" one which guide the user to
> > use apport rather than having to deal with gdb to get the informations
> >
>
> I think the first step should be what you said, ask to the reporter for
> a apport report and if the auto retracer doesn't work then probably ask
> for the possibility of get one with gdb.

    Actually, I often find gdb-generated backtraces to be of strictly
limited utility, unless the reporter happens to have all the relevant
-dbgsym packages installed, and will likely work on reproducing the
bug from the description, rather than trying to understand the
backtrace.  If apport can't upload the report, and the reporter can
manually upload the apport-generated report file, it's then easier to
get a useful stacktrace by retracing.

-- 
Emmet HIKORY