Re: help tracking down an uninitialized value (with Valgrind output)

2016-09-30 Thread Scott Kostyshak
On Thu, Sep 29, 2016 at 07:12:40PM -0700, Pavel Sanda wrote: > Scott Kostyshak wrote: > > How did you know it was preview_error_? I'm searching for bug-fixing > > intuition. > > valgrind log -> LaTeX.cpp:115 -> clean_start -> buffer.lastPreviewError() > [Converter.cpp:656] -> > d->preview_error_

Re: help tracking down an uninitialized value (with Valgrind output)

2016-09-29 Thread Pavel Sanda
Scott Kostyshak wrote: > How did you know it was preview_error_? I'm searching for bug-fixing > intuition. valgrind log -> LaTeX.cpp:115 -> clean_start -> buffer.lastPreviewError() [Converter.cpp:656] -> d->preview_error_ [Buffer.cpp:1200] -> preview_error_ [Buffer.cpp:452] is set in

Re: help tracking down an uninitialized value (with Valgrind output)

2016-09-29 Thread Scott Kostyshak
On Wed, Sep 28, 2016 at 09:18:37PM -0700, Pavel Sanda wrote: > Scott Kostyshak wrote: > > I would appreciate it if someone were able to teach me how the steps to > > take to fix find the root issue. > > bunch of variables are not initialized in Buffer::Impl::Impl (unless cloning > buffer) >

Re: help tracking down an uninitialized value (with Valgrind output)

2016-09-28 Thread Pavel Sanda
Scott Kostyshak wrote: > I would appreciate it if someone were able to teach me how the steps to > take to fix find the root issue. bunch of variables are not initialized in Buffer::Impl::Impl (unless cloning buffer) quick check show these: layout_position preview_file_

help tracking down an uninitialized value (with Valgrind output)

2016-09-28 Thread Scott Kostyshak
I am trying to investigate what I think is a bug where sometimes when I compile sk/Intro.lyx with system fonts + LuaTeX it gives an error and sometimes not. I wouldn't be surprised if the Valgrind error I see has nothing to do with it, but nonetheless it seems important. I get the following