Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions

[Thomas Hackert <thackert@nexgo.de>]

Hello Rene, *,
On Sun, Aug 14, 2016 at 12:01:15PM +0200, Rene Engelhard wrote:
> On Sat, Aug 13, 2016 at 02:34:32PM +0200, Thomas Hackert wrote:
> > > On Sat, Aug 13, 2016 at 12:19:44PM +0200, Thomas Hackert wrote:
> > > > while trying to get a backtrace for a crash with an installed
> > > > extension, I started LO from command line with "soffice
> > > > --backtrace". To my astonishment LO crashes, when
> > > 
> > > You mean it only happens with --backtrace or also without? Your title
> > > suggests the first.
> > 
> > Yes. It only happens if I start LO from command line with "soffice
> > --backtrace".
> 
> OK, then IMHO it's even minor, since normal users won't do that :)

Well, but people in QA at LO or some users trying to get a backtrace
to report a bug ... ;)

> > > But yes, if you want a --backtrace, you DO need the -dbgsym packages. They
> > > contain the debug symbols. Without them a backtrace not very useful.
> > 
> > But still it should not crash immediately ... ;)
> 
> That's true. I was aiming at your "I don't want to install the -dbgsym packages".

But how do I install the debug packages? Neither "apt-cache search
libreoffice dbg" or "libreoffice debug" show anything. "apt-cache
search dbgsym" does only show mariadb, openhpi packages and owfs-dbg
... :( Do I need an special entry to my sources.list?
Have a nice day
Thomas.

-- 
<Thoth_> Yeah, well that's why it's numbered 2.3.1... it's for those of us
         who miss NT-like uptimes