On Sun, Jul 21, 2019 at 01:27:36PM +0200, Kornel Benko wrote:
> Am Sonntag, 21. Juli 2019, 13:15:02 CEST schrieb Jürgen Spitzmüller:
> > Am Sonntag, den 21.07.2019, 12:55 +0200 schrieb Kornel Benko:
> > > Breakpoint 1, lyx::Buffer::Impl::Impl(lyx::Buffer*,
> > > lyx::support::FileName const&, bool,
Am Sonntag, 21. Juli 2019, 13:15:02 CEST schrieb Jürgen Spitzmüller:
> Am Sonntag, den 21.07.2019, 12:55 +0200 schrieb Kornel Benko:
> > Breakpoint 1, lyx::Buffer::Impl::Impl(lyx::Buffer*,
> > lyx::support::FileName const&, bool, lyx::Buffer const*)
> > (this=0x1ca62f0, owner=0x1ca7fa0, file=...,
Am Sonntag, den 21.07.2019, 12:55 +0200 schrieb Kornel Benko:
> Breakpoint 1, lyx::Buffer::Impl::Impl(lyx::Buffer*,
> lyx::support::FileName const&, bool, lyx::Buffer const*)
> (this=0x1ca62f0, owner=0x1ca7fa0, file=...,
> readonly_=false, cloned_buffer=0x0) at /usr2/src/lyx/lyx-
> git/src/Buf
Am Sonntag, 21. Juli 2019, 06:23:12 CEST schrieb Scott Kostyshak:
> With ebf42d9b, I get the attached backtrace when doing lyx -e pdf2
> Welcome.lyx.
>
> Can anyone reproduce?
>
> Scott
Yes.
Breakpoint 1, lyx::Buffer::Impl::Impl(lyx::Buffer*, lyx::support::FileName
const&, bool, lyx::Buffer c
With ebf42d9b, I get the attached backtrace when doing lyx -e pdf2 Welcome.lyx.
Can anyone reproduce?
Scott
lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and send us
a bug report
