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

Dorothy Freeman dfreeman at pacbell.net
Mon Apr 14 13:16:13 EDT 2014


Hello Geert,

Sorry, it appears like I failed to get the attachments into the email 
I sent earlier.

I have gone through all the reports and attached a pdf of which ones 
worked and which failed.   Some that did not cause the crash seemed 
to be those with no data to report.   Assets & Liabilities and Income 
& Expense which should have data to report mostly failed.

I also zipped the logs created during the tests.  I did not find any 
new gnucash.trace..... files created during the time I was doing all 
these tests.

Dorothy

At 01:38 AM 4/2/2014, Geert Janssens wrote:

>I have looked at the log files. Unfortunately they don't reveal why 
>running a report crashes GnuCash. So we'll have to dig deeper.
>
>
>
> From your original message I find that you are using GnuCash 2.6. I 
> did fix a crash regarding reports in GnuCash 2.6.3 which got 
> released this weekend. You may want to try this version.
>
>
>
>I also see in the logs you sent that some reports were at least 
>generated if not displayed. Do you experience the crash with all reports ?
>
>
>
>Geert
>
>
>
>On Tuesday 01 April 2014 22:02:24 Dorothy Freeman wrote:
>
> > Thanks again for the responses. Sorry I forgot to say the system
>
> > files are visible, not hidden.
>
> > I don't know why my search programs didn't find them but here they
>
> > are. Thanks so much for the help.
>
> >
>
> > Dorothy
>
> >
>
> > At 04:57 AM 4/1/2014, Dave H wrote:
>
> > >Hopefully this will help you find your GnuCash log files..
>
> > >
>
> > >This is under Win 8.1 but I seem to recall it was the same under Win
>
> > >7 - I usually just open Windows Explorer and navigate to the
>
> > >C:\Users\<user name> folder, then I click just after the folder name
>
> > >that explorer displays partway down the window i.e. at the end of
>
> > >the "This PC > OSDISK(C:) > Users > <username> " which changes it
>
> > >to "C:\Users\<username>" and then I type in the "\appdata" and hit
>
> > >enter. This displays the AppData folder and the 3 folders contained
>
> > >in it - Local, LocalLow and Roaming. Once this is done I just
>
> > >double click on the "Local" folder name and then the "Temp" folder
>
> > >name and I'm there ...
>
> > >
>
> > >I see that there are quite a few gnucash.trace.xxxxxx.log files in
>
> > >there that I've never bothered to look at before now :-)
>
> > >
>
> > >Cheers Dave H.
>
> > >
>
> > >
>
> > >
>
> > >On 1 April 2014 17:33, Geert Janssens
>
> > ><<mailto:janssens-geert at telenet.be>janssens-geert at telenet.be> wrote:
>
> > >
>
> > >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
>
> > > > > >
>
> > > > > > <<mailto:dfreeman at pacbell.net>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>http://wiki.gnucash.org/w
>
> > >
>
> > > iki/Tracefile
>
> > >
>
> > > > > > Do all reports crash, or just some? Could you be running into
>
> > > > > > the
>
> > > > > > bug
>
> > > > > >
>
> > > > > > fixed in
>
> > >
>
> > > <<https://github.com/Gnucash/gnucash/commit/a48e656e>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
>
> > >
>
> > >_______________________________________________
>
> > >gnucash-user mailing list
>
> > ><mailto:gnucash-user at gnucash.org>gnucash-user at gnucash.org
>
> > >https://lists.gnucash.org/mailman/listinfo/gnucash-user
>
> > >-----
>
> > >Please remember to CC this list on all your replies.
>
> > >You can do this by using Reply-To-List or Reply-All.
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GNU_Reports_Tab_Errors.pdf
Type: application/pdf
Size: 34184 bytes
Desc: not available
URL: <http://lists.gnucash.org/pipermail/gnucash-user/attachments/20140414/c20e5dd3/attachment-0001.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gcashdata_4.gnucash.20140408110501.zip
Type: application/zip
Size: 12444 bytes
Desc: not available
URL: <http://lists.gnucash.org/pipermail/gnucash-user/attachments/20140414/c20e5dd3/attachment-0001.zip>


More information about the gnucash-user mailing list