No, as upstream explained, in this case the null indicates invalid internal state, so the correct behavior for the program is indeed to halt the program execution and for you it is to find out how the invalid internal state occurs in the first place through debugging or similar.
Alex Alex On Mon 20. Dec 2021 at 12.12, Ranjitsinh Rathod < ranjitsinhrathod1...@gmail.com> wrote: > Steve, > > Earlier we have also thought the same things from the upstream issue > comment and we have tried another workaround mentioned on the ticket which > is disabled epoll. > We have tried it and it didn't work for the project. we still facing the > issue. > > Then we tried the NULL check for the variable. Maybe it's not a proper fix > (just a workaround to check the pointer before accessing), but there is > nothing wrong with checking the null before accessing any variable. > > Ranjitsinh > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#159855): https://lists.openembedded.org/g/openembedded-core/message/159855 Mute This Topic: https://lists.openembedded.org/mt/87787403/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
