segfault in new ledger code

Jack ostroffjh at users.sourceforge.net
Fri Jan 10 21:54:48 GMT 2020


On 2020.01.10 16:48, Thomas Baumgart wrote:
> On Freitag, 10. Januar 2020 22:06:56 CET Jack wrote:
> > On 2020.01.10 15:34, Jack wrote:
>>> Per your suggestion in the Wayland thread, I just recompiled with  
>>> UNFINISHEDFEATURES enabled.  Selecting the new ledger gives me an  
>>> immediate segfault, from both 5.0 and master, and whether or not I  
>>> have already selected an account.  I'm pretty sure I can easily  
>>> enough get a backtrace, but before I do, what other information  
>>> would you want to help debug?
> > >
>> Sorry - I forgot on important point - these segfaults are all using  
>> X11.  I do have Wayland available, but it's not very stable, so I'll  
>> test with Wayland a bit later.  I figure unless the crash is  
>> specifically X related, it would likely crash under wayland also.
> 
> Too bad that it crashes for you. Can you try to do this with an empty  
> file just to make sure it is not related to your data? I expect it to  
> be your data since it does not crash for me.

I suppose I should have known my data would crash things.....  No  
strange behavior with git master under X11, with a new file and only  
one transaction.  Hopefully I'll have time to try under Wayland shortly.

Jack


More information about the KMyMoney-devel mailing list