Re: Valgrind: conditional jump or move depends on uninitalized value(s)

On Fri, Jun 21, 2024 at 05:24:16PM GMT, Jean-Marc Lasgouttes wrote: > Le 20/06/2024 à 20:03, Scott Kostyshak a écrit : > > This report is from opening LyX, starting a new document, and quitting. > > How can I read it to know if it's LyX's fault or not? Specifically, how > > can I know whether the u

Re: valgrind: points to unaddressable byte(s)

On Fri, Jun 21, 2024 at 04:16:32PM GMT, Pavel Sanda wrote: > On Thu, Jun 20, 2024 at 02:00:08PM -0400, Scott Kostyshak wrote: > > When I export the English Welcome.lyx on the command line with the > > following command: > > > > lyx -e default Welcome.lyx > > > > I get the following output: > >

Re: Valgrind: conditional jump or move depends on uninitalized value(s)

Le 20/06/2024 à 20:03, Scott Kostyshak a écrit : This report is from opening LyX, starting a new document, and quitting. How can I read it to know if it's LyX's fault or not? Specifically, how can I know whether the uninitialised value is created inside QPainter::drawPixmap() or if it's instead i

Re: valgrind: points to unaddressable byte(s)

On Thu, Jun 20, 2024 at 02:00:08PM -0400, Scott Kostyshak wrote: > When I export the English Welcome.lyx on the command line with the following > command: > > lyx -e default Welcome.lyx > > I get the following output: > > ==8181== Syscall param waitid(infop) points to unaddressable byte(s) >