segmentation fault

[Mark Johnson]

Derek Atkins wrote:

>Mark Johnson <mrj001 at shaw.ca> writes:
>  
>
[snip]

>>    Uh, this is wrong.  There's no reason you should have had to restore
>>    >From backup...
>>
>>Why?  This seems to have solved the crash on open.  I may have left
>>the multicolumn report open when I closed gnucash.  Does it reopen a
>>report that was left open when gnucash was last closed?  If so, it
>>would explain the crash on startup.  And if this fact is saved in
>>the "books" file, it would explain why my restore from backup
>>helped.
>>    
>>
>
>Wait, did you move your data file, or did you move the file
>~/.gnucash/books/<your-data-file-path>?  Your report information is
>stored in the latter; it is NOT stored in your data file.  And yes,
>gnucash remembers which reports are open (on a per-data-file basis)
>and re-opens and re-runs the reports on startup.
>
>  
>
I moved the data file.  I guess that this fixed my crash on startup due 
to gnucash no longer trying to rebuild the report on startup.

>>        There is a new "multicolumn view" under Reports->Custom.  This, I 
>>        presume, is my saved report.  It continues to crash gnucash.
>>
>>    Does it crash when you run the report?  Or when you load gnucash?
>>    I'm still confused.
>>
>>It now crashes only when I run the report.  Prior to the restore from backup, it
>>was crashing on load.
>>    
>>
>
>Probably because you had the report open when it you closed gnucash;
>so it tried to rebuild the report.  Was anything interesting displayed
>in the terminal when you start gnucash?
>
>  
>
Only the "segmentation fault".

>>I had moved the original data file to a temp directory.  Once I was satisfied that
>>I had fixed the problem, I had planned to remove it.  It was only two transactions
>>so no big deal.  I haven't removed it yet, though.
>>    
>>
>
>Just move it back.  Although gnucash remembers report configuration
>based on the full filename.
>  
>
Given that gnucash remembers that I had the report open for that data 
file, and that I have now fixed the currency problem from the log 
replay, I'll leave it as is.  This will keep gnucash from re-running the 
faulty report on startup (and crashing).

Mark