This is a very old and very heavily in use application. Think interpreted language. There are many developers. There is something ubuntu 22 specific that doesn't happen on RH 9 going on with shared memory. I did fix (they were not the cause of any issue) those 2 places temporarily and I am still getting this.
Attached is a clean run without valgrind errors that still gets the shared memory attachment message when run through valgrind.
This is a very old and very heavily in use application. Think interpreted language. There are many developers. There is something ubuntu 22 specific that doesn't happen on RH 9 going on with shared memory. I did fix (they were not the cause of any issue) those 2 places temporarily and I am still getting this.
Attached is a clean run without valgrind errors that still gets the shared memory attachment message when run through valgrind.
pmilosla@ pmilosla- ubuntu22: mgr> grep memory valgrind_ log_226662. txt pmilosla- ubuntu22: mgr> sudo valgrind --verbose --tool=memcheck --log-file= valgrind_ log_%p. txt --trace- children= yes --leak-check=full --show- leak-kinds= all --track-origins=yes ../bin/irisdb -s. pmilosla- ubuntu22: mgr> sudo ../bin/irisdb -s.
==226662== Memcheck, a memory error detector
pmilosla@
Unexpected error occurred attempting to attach to shared memory.
pmilosla@
Node: pmilosla-ubuntu22, Instance: LATEST
USER>h pmilosla- ubuntu22: mgr>
pmilosla@