segfault in new ledger code

[Thomas Baumgart]

On Freitag, 10. Januar 2020 22:06:56 CET Jack wrote:

> On 2020.01.10 15:34, Jack wrote:
> > Thomas,
> > 
> > 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?
> > 
> > Jack
> 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.

Thanks for your help.

-- 

Regards

Thomas Baumgart

https://www.signal.org/       Signal, the better WhatsApp
-------------------------------------------------------------
'I think there is a world market for maybe five computers.'
 -Thomas Watson, Chairman of IBM, 1943
-------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 868 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kmymoney-devel/attachments/20200110/dc6db7a6/attachment.sig>