Bug#766788: libreoffice-writer: Crashes with "stack smashing detected"
On Mon, Oct 27, 2014 at 11:24:43AM +0100, Michal Sojka wrote:
> >> I can reproduce this in both unstable and testing
> >> (1:4.3.3~rc2~git20141011-1). I cannot reproduce this in the version
> >
> > And why are you then not marking it as such?
>
> How can I do that next time? https://www.debian.org/Bugs/Reporting does
> not mention how to mark multiple version.
You add 1:4.3.3~rc2~git20141011-1 in Version: and the BTS then knows
it also affect 1:4.3.3~rc2-1 (see [1])
> >> from libreoffice.org (LibreOffice_4.3.2_Linux_x86-64_deb.tar.gz).
> >
> > And with 4.3.3 rc1? (Or rc2 which would be in the next days)
> > You right now compare a 4.3.2 with a -between-4.3.3-rc1-and-rc2
> > or 4.3.3 rc2 ;)
> >
> >> After the crash the following information appears on the terminal:
> >>
> >> *** stack smashing detected ***: /usr/lib/libreoffice/program/soffice.bin terminated
> >> ======= Backtrace: =========
> >> /lib/x86_64-linux-gnu/libc.so.6(+0x72faf)[0x7fdd44a1ffaf]
> >> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7fdd44aa30a7]
> >> /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7fdd44aa3070]
> >
> > But given it runs into the fortify functions it probably won't appear
> > in 4.3.3 rc1 upstream until it's a real crash also there; upstream doesn't
> > use those hardening flags.
>
> I was able to reproduce this in my own build of libreoffice. Any hint
But probably without hardening or with? Same backtrace or something else?
> how to best debug this with gdb?
I've so far sucessfully avoided this except getting a bt - which we already
have ;) Job for upstream :)
Regards,
Rene
[1] https://bugs.debian.org/cgi-bin/version.cgi?info=1;absolute=0;collapse=1;found=libreoffice%2F1%3A4.3.3~rc2~git20141011-1;found=libreoffice%2F1%3A4.3.3~rc2-1;package=libreoffice-writer
Reply to: