[Evolution-hackers] detecting new ical memory tracking


I now have the situation that I feared in issue #516408: SyncEvolution
trunk uses libical calls where the returned string must be freed when
SyncEvolution runs with Evolution 2.22 and must not be freed when run
with older Evolution releases. My plan still is to only provide only one
binary for 2.10, 2.12, 2.22, therefore I need the runtime detection of
the API change that I suggested in

Introducing the code rewrite suggested by Michael is impossible. Can I
have the less intrusive patch included on trunk and the stable branch,
please? Or is there some other version number which can be queried at
runtime? I'd rather not parse /proc/self/maps to find out what the
revision of libecal is... As discussed in #516408, checking the version
number would be sub-optimal.

FWIW, the leak shows up nicely in the nightly testing:

Bye, Patrick Ohly
Patrick Ohly gmx de

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]