Thanks guys,I will poke around in it some more. Good to know that 5.13 is not the problem in itself.
I will see if there is anything helpful in the event log as well. I have debugging information for the subusrface app working fine, it is MXE+QT which is difficult to get anything useful out of, and the build time discourages experimentation with build flags :-) I was curious to know if other people had the same issue, as knowing any commonalities/differences can help locating an issue. Paul On Tue, Sep 3, 2019 at 4:44 AM Thiago Macieira <thi...@macieira.org> wrote: > On Monday, 2 September 2019 02:23:09 PDT Paul Buxton wrote: > > I think it might be because we are trying to access the selected product > > before it has been populated, but my Qt-fu is not strong enough to be > > certain yet, and the latest MXE doesn't support building > Debug-and-Release > > for the QT libraries so it isn't clear exactly where the exception is > being > > generated. > > You shouldn't need a debug-and-release build to debug. You can do it the > Unix > way and build an unsuffixed library with debug symbols and without > optimisation. > > -- > Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org > Software Architect - Intel System Software Products > > > > _______________________________________________ > subsurface mailing list > subsurface@subsurface-divelog.org > http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface >
_______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface