bug in clCkptSectionIterationNext

Submitted by edrt on Mon, 2007-03-19 05:39.
::

Hi All,

Find bug in clCkptSectionIterationNext during debugging:

secId is not initialized, thus when clCkptSectionIterationNext has no more sections to return, exitOnError will erroneousely clOsalFree(secId.id), thus corrupt other data structure and mess things up.

Regards
Eddy

‹ bug in ioc route cpmComponentUnregister problem ›
bug in
Submitted by harikrishna_gp on Mon, 2007-03-19 10:52.

Eddy,
Thanks for letting us know this. This is indeed a bug. However I am sure its a rare case. We have entered it in our bug data base and the fix will be part of next release. Uninitialized stack variables are always dangerous.

Thanks,
Hari

bug in
Submitted by edrt on Mon, 2007-03-19 19:26.

Hi Hari

BTW, to be SAF conformant, clCkptSectionIterationNext should return SA_AIS_ERR_NO_SECTIONS when there are no more sections to return (instead of return SA_AIS_ERR_NOT_EXIST)

Thanks
Eddy