Started by an SCM changeBRANCHmasterEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.org laforge@gnumonks.org0000502050201.0700070000120206999699910583e8ed086615e49a89f4e6899285528e3c4cba2583e8ed086615e49a89f4e6899285528e3c4cba2origin/master583e8ed086615e49a89f4e6899285528e3c4cba2583e8ed086615e49a89f4e6899285528e3c4cba2origin/master583e8ed086615e49a89f4e6899285528e3c4cba2583e8ed086615e49a89f4e6899285528e3c4cba2origin/masterhttps://gerrit.osmocom.org/onomondo-ipahttps://jenkins.osmocom.org/jenkins/job/master-onomondo-ipa/10/artifacthttps://jenkins.osmocom.org/jenkins/job/master-onomondo-ipa/changeshttps://jenkins.osmocom.org/jenkins/job/master-onomondo-ipa/10/https://jenkins.osmocom.org/jenkins/job/master-onomondo-ipa/10/testReportfalse#1050204881master-onomondo-ipa #1010falsefalse10156460SUCCESS1782807607282https://jenkins.osmocom.org/jenkins/job/master-onomondo-ipa/10/- src/ipa/libipa/es10b_get_euicc_info.cc5f1b20c10ab90ebc195d5f3c064252999d81a501782289530000https://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.depmaier@sysmocom.dees10b_get_euicc_info: add explanatory comments regarding EUICCInfo2
onomondo-ipa has a built-in IoT eUICC emulation. This means that we
have to deal with two different EUICCInfo2 formats, which requires
additional logic in ipa_es10b_get_euicc_info_free to free the
allocated structs correctly. Since it is not immediately obvious
how the logic works, let's add some explanary comments to make it
obvious.
Related: SYS#8101
Change-Id: I282fa91a4099a771a353101b0ce17ae3daae9c42
2026-06-24 10:25:30 +0200c5f1b20c10ab90ebc195d5f3c064252999d81a50es10b_get_euicc_info: add explanatory comments regarding EUICCInfo2editsrc/ipa/libipa/es10b_get_euicc_info.c
- src/ipa/scard.c583e8ed086615e49a89f4e6899285528e3c4cba21782289530000https://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.depmaier@sysmocom.descard: add comment about memory-leak in libpcsclite
As it seems, SCardReleaseContext does not free all of the memory
allocated by SCardEstablishContext. The probem has no real-world
impact, but still showas up in valgrind. Let's add a comment so
that we do not forget what causes the leak.
Related: SYS#8101
Change-Id: I5224f3824ce2ad33e678cd859ad28c47788dbb24
2026-06-24 10:25:30 +0200583e8ed086615e49a89f4e6899285528e3c4cba2scard: add comment about memory-leak in libpcscliteeditsrc/ipa/scard.c
githttps://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.depmaierBRANCHmasterEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.org laforge@gnumonks.orgStarted by upstream project "master-onomondo-ipa" build number 1010master-onomondo-ipajob/master-onomondo-ipa/0000340034001.000010583e8ed086615e49a89f4e6899285528e3c4cba2583e8ed086615e49a89f4e6899285528e3c4cba2origin/master583e8ed086615e49a89f4e6899285528e3c4cba2583e8ed086615e49a89f4e6899285528e3c4cba2origin/master583e8ed086615e49a89f4e6899285528e3c4cba2583e8ed086615e49a89f4e6899285528e3c4cba2origin/masterhttps://gerrit.osmocom.org/onomondo-ipafalse#1034003351master-onomondo-ipa ยป a1=default,a2=default,a3=default,a4=default,osmocom-master #1010falsefalse10156461SUCCESS1782807607282https://jenkins.osmocom.org/jenkins/job/master-onomondo-ipa/a1=default,a2=default,a3=default,a4=default,label=osmocom-master/10/build5-deb12build-ansible- src/ipa/libipa/es10b_get_euicc_info.cc5f1b20c10ab90ebc195d5f3c064252999d81a501782289530000https://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.depmaier@sysmocom.dees10b_get_euicc_info: add explanatory comments regarding EUICCInfo2
onomondo-ipa has a built-in IoT eUICC emulation. This means that we
have to deal with two different EUICCInfo2 formats, which requires
additional logic in ipa_es10b_get_euicc_info_free to free the
allocated structs correctly. Since it is not immediately obvious
how the logic works, let's add some explanary comments to make it
obvious.
Related: SYS#8101
Change-Id: I282fa91a4099a771a353101b0ce17ae3daae9c42
2026-06-24 10:25:30 +0200c5f1b20c10ab90ebc195d5f3c064252999d81a50es10b_get_euicc_info: add explanatory comments regarding EUICCInfo2editsrc/ipa/libipa/es10b_get_euicc_info.c
- src/ipa/scard.c583e8ed086615e49a89f4e6899285528e3c4cba21782289530000https://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.depmaier@sysmocom.descard: add comment about memory-leak in libpcsclite
As it seems, SCardReleaseContext does not free all of the memory
allocated by SCardEstablishContext. The probem has no real-world
impact, but still showas up in valgrind. Let's add a comment so
that we do not forget what causes the leak.
Related: SYS#8101
Change-Id: I5224f3824ce2ad33e678cd859ad28c47788dbb24
2026-06-24 10:25:30 +0200583e8ed086615e49a89f4e6899285528e3c4cba2scard: add comment about memory-leak in libpcscliteeditsrc/ipa/scard.c
githttps://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.de