Hi Pierre, I did the tests that you propose on both emails and I achieved the same results. I will file two bugs on pymaemo bugzilla[1] and will take a look on this as soon as possible. Thanks for your reports!
Regards, Luciano -INdT- [1] https://garage.maemo.org/tracker/?atid=229&group_id=40&func=browse On 2/11/07, Pierre Amadio <[EMAIL PROTECTED]> wrote:
Hi there. As a followup of my previous message (problem using dbus rpc call with argument in python) i decided to give rpc_async_run a try instead of rpc_run. Now, not only it 'does not work', but pyhton2.5 segfault as well. I guess i did something wrong like not having an osso context properly set or something like this, but i also feel it should be up to libosso or python-osso to check the argument it use ar ok, shouldnt it ? I have attached a test cased based on : http://maemo.org/platform/docs/python-bora/python_maemo_howto.html#Introduction+to+LibOSSO I also try to catch a backtrace, with 'gdb /usr/bin/python2.5 core' , but i m not that familiar with gdb, nor do i know where to get the python-osso debug symbols. Anyway, the begining of the backtrace looks like this: #0 0xb72d068c in _python_to_rpc_t () from /usr/lib/python2.5/site-packages/osso/rpc.so #1 0xb72cfc61 in Context_rpc_run_with_defaults () from /usr/lib/python2.5/site-packages/osso/rpc.so #2 0xb79f09b9 in osso_rpc_run () from /usr/lib/libosso.so.1 Am i wrong in thinking there is something wrong in python-osso ? I use python2.5-osso 0.2-1osso1. _python_to_rpc_t is defined in python-osso/src/osso-helper.c, but this is where i m stuck at, not understanding what may be wrong there (i guess one of the 2 argument being sent has not the right type or size or something, but that s about it). Any help would be appreciated. Pierre Amadio _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
_______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
