Hi, I am facing a strange issue in vec_validate.
I use an incrementing id and keep doing a vec_validate based on that id for a certain single dimensional array of structures. Each structure in the array itself is 216 bytes long. Around the time when the id reaches 1.3 million, the vec_validate seems to be corrupting another data structure for which a clib_mem_alloc was done separately and only once. I circumvented the problem by knocking off the vector for which I was doing a vec_validate of, by using an array for which I allocated memory once at the beginning using clib_mem_alloc (fortunately I know at startup what will be the max value ever of my incrementing id) and the usecase works well for me and everybody is happy. But now I don't have a root cause to explain except to give some dodgy story. So my question -- is it at all possible that vec_validate can lead to such issues or I have just been able to throw something under the carpet which will stink one day in my usecase ? I am at VPP 18.01 Regards -Prashant
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12229): https://lists.fd.io/g/vpp-dev/message/12229 Mute This Topic: https://lists.fd.io/mt/29738945/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
