> On Dec 14, 2014, at 1:52 AM, Marcus Wellnitz <mar...@wellnitzfamily.de> wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello, > > I've made some improvements with the latex-invoice examples and got it > working for my Ubuntu 14.04 LTS environment. (Mostly adapted to new > python version) > > It worked until some updates between November 3 and November 10. I could > not handle to revert all of the involving upgrades so can't say which > one did the minor changes that lead to the error. :-( > > In file: latex_invoice.py (gnucash-python-examples) > session = gnucash.Session(input_url,ignore_lock=ignore_lock) > > ==> Coredump, no Stacktrace! > > Error: > * 01:02:18 CRIT <GLib> g_date_time_format: assertion 'datetime != > NULL' failed > * 01:02:18 CRIT <GLib> g_date_time_unref: assertion 'datetime != > NULL' failed > Segmentation fault (core dumped) > > > I can follow the error up to: > /usr/lib/python2.7/dist-packages/gnucash/gnucash_core_c.py > def qof_session_load(*args): > """qof_session_load(QofSession * session, QofPercentageFunc > percentage_func)""" > return _gnucash_core_c.qof_session_load(*args) > > After executing _gnucash_core_c.qof_session_load(*args) > The error appears. > > Until the upgrades all was working like a charme. > > Mo, 03. Nov 2014 17:09:47 +0200 > [AKTUALISIERUNG] libglib2.0-0:amd64 2.40.0-2 -> 2.40.2-0ubuntu1 > [AKTUALISIERUNG] libglib2.0-0:i386 2.40.0-2 -> 2.40.2-0ubuntu1 > [AKTUALISIERUNG] libglib2.0-bin:amd64 2.40.0-2 -> 2.40.2-0ubuntu1 > [AKTUALISIERUNG] libglib2.0-data:amd64 2.40.0-2 -> 2.40.2-0ubuntu1 > [AKTUALISIERUNG] python3-software-properties:amd64 0.92.37.1 -> 0.92.37.2 > > Mo, 10. Nov 2014 20:11:40 +0200 > [AKTUALISIERUNG] python3-uno:amd64 1:4.2.6.3-0ubuntu1 -> 1:4.2.7-0ubuntu1 > > > Maybe someone can help me?
Since the only changes on maint between 3 and 10 November were translations and in Guile, I suppose that you're using master. We landed Aaron's KvpFrame reimplementation on 3 November and nothing much else through the 10th. Did you regenerate the swig files? You'll need to do that often on master. If you build in a separate directory you'll need to `git clean -fdx` in your source directory then re-run autogen.sh and configure. If you build in-source `make distclean` should do it. Do the tests in src/optional/python-bindings pass? If they do, is your reporting code in a public repo somewhere? `git bisect` automatically runs a binary search on a range of commits to help you find the exact commit that broke something. Regards, John Ralls _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
