Thanks, I'll check them out. On Tue, Feb 5, 2019 at 4:43 PM John Ralls <[email protected]> wrote:
> > > > On Feb 5, 2019, at 6:35 AM, David Carlson <[email protected]> > wrote: > > > > On Tue, Feb 5, 2019, 5:30 AM Bostjan Vilfan <[email protected] wrote: > > > >> I tried both, gnucash 3.4 as well as 2.6.26; therefore it could be > >> something with Windows 10 version 1809; in case you are able to figure > out > >> something, I am enclosing link to Windows msinfo results: > >> > > > > > >> Regards, > >> bostjanv > >> > >>> ______ > >>> > >>> > > There are instructions in the Gnucash wiki on how to get error messages > out > > of Gnucash, I am not online right now, so I cannot tell you exactly > where, > > I just remember that it is not an easy task. > > > > There is also a way to start Gnucash from the command line without a data > > file. Sometimes a bad data file can cause a crash. Again the exact > > procedure escapes me, but other users or devs may be able to help. > > > > Sorry I cannot be more help right now. > > The instructions are at https://wiki.gnucash.org/wiki/Tracefile and > https://wiki.gnucash.org/wiki/stack_trace. The trace file is easy. The > stack trace is hard only on windows, but is the most useful when you have a > crash. > > Please don't post either here: Crashes deserve bug reports. > > Regards, > John Ralls > > _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
