Runtime crash when running reports: Update with event view error report

[Geert Janssens]

On Monday 31 March 2014 12:21:07 Dorothy Freeman wrote:
> Mike & Derek,
> Thank you both for the suggestions.  I have been researching the
> information you provided.  I've gone through all the files on my
> computer and have not been able to find any
> gnucash.trace.ABCDEF  file anywhere.   I have also gone through any
> file referencing "Guile" and only find them in the program
> area.  Nothing that looks like it would have information about the
> crash.   This is on Win7.
> 
Guile is indeed a program. It is also a programming language. Most reports are written in this 
programming language. That's what Mike was explaining. You won't find information about the 
crash in the program area.

The crash reports go into
c:\Users\<yourusername>\AppData\Local\Temp

You should replace <yourusername> with the effective name of the user of your PC. Usually 
that is the same or similar as what you see on the login screen.

Note that depending on how your Windows is configured the "Local" directory is hidden. To 
view its content you will have to edit the directory options for the AppData directory. I don't 
have a Windows 7 myself, so I can't give you the exact details of how to do this. Perhaps 
someone else can fill this gap.

The fact that this directory is hidden is probably also why you couldn't find any 
gnucash.trace.<something> files.

Geert

> Unfortunately I don't think I'm going to be able to use GnuCash which
> is unfortunate.  It is easier than Quicken and the instructions are
> fabulous.
> 
> Dorothy
> 
> At 01:12 AM 3/27/2014, Geert Janssens wrote:
> >On Wednesday 26 March 2014 20:01:38 Mike Alexander wrote:
> > > --On March 26, 2014 12:58:47 PM -0700 Dorothy Freeman
> > > 
> > > <dfreeman at pacbell.net> wrote:
> > > > I have completed all the updates to the Runtime c++ library with
> > > > no
> > > > 
> > > > change. Reports still crash.
> > > > 
> > > > We're trying to use GnuCash for a non-profit and need to keep
> > > > costs
> > > > 
> > > > low. Without the reports option the program is of no use to us.
> > > > 
> > > > Help would be appreciated.
> > > 
> > > There is not enough information here for anyone to know what the
> > > real
> > > 
> > > problem is. All this says is that GnuCash crashed somewhere in
> > > Guile,
> > > 
> > > which given that Guile is used to produce reports isn't very
> > > 
> > > informative. We need at least a Guile stack trace and perhaps a C
> > > 
> > > stack trace to help. I don't use Windows and have no idea how to
> > > get
> > > 
> > > either of these. If you can find where GnuCash put its console
> > > 
> > > output, there might be a Guile stack trace there. Sorry I can't be
> > > 
> > > of more help.
> >
> >Usually when a report causes problems you can find more details in
> >the trace file that gets written by GnuCash. How to obtain this
> >trace file can be found here:
> >
> >http://wiki.gnucash.org/wiki/Tracefile
> >
> > > Do all reports crash, or just some? Could you be running into the
> > > bug
> > > 
> > > fixed in <https://github.com/Gnucash/gnucash/commit/a48e656e>? I
> > > 
> > > haven't seen this crash myself, but it caused very large reports
> > > to
> > > 
> > > crash.
> >
> >This is unlikely the issue on Windows. The bug you refer to only
> >affected builds with guile 2. The windows build is still using guile
> >1.8.
> >
> >
> >
> >Geert