[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[Jack via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360938

--- Comment #12 from Jack <ostroffjh at users.sourceforge.net> ---
Well, if you don't have a backup copy of the small database before fixing, then
capturing the fixes is no longer an option.

Different sizes of databases containing the same content does not surprise me
too much - there are lots of local configuration issues like block size,
minimum table size, ... (I'm mainly guessing, but I do have some database
background.)

Unfortunately, it sounds like running a debugger would be too difficult for
you.  The simple explanation is that you run the debugger, and it runs
KMyMoney.  If it has the right information (source code and debugging symbols
compiled in) then you can watch how it runs in the source code, and can set
breakpoints (places it just stops for further instructions instead of just
going on.)  It can be very useful for a developer, as you can also examine the
value of variables, so if you know where it blows up, you can set a breakpoint
a few lines earlier, or before it calls that function, and explore the state of
things right before the problem.  Unfortunately, it is not something to learn
quickly.  

One thing I just thought of - can you reinstall an earlier  version, where you
were not getting the crash?  If so, you might be able to save as a file, or
even as an anonymized file.  Then you could try the new version, or submit the
anonymized file to the developers.  (An anonymized file changes all account
numbers and all actual financial values - changing them to random values.)

I suppose it would be helpful if we could replicate the consistency checks as
sql queries, but I'm not sure how difficult that would be.  Maybe one of the
developers who works specifically on the database back end can make a
suggestion.

-- 
You are receiving this mail because:
You are the assignee for the bug.