Gah, I guess loading libmirprotobuf.so.0 and libmirprotobuf.so.1 in the same process is more common than I thought since the mirclientplatformmesa module links against libmirclient.
The mako test runner will install the mesa platform modules from the CI build; when glmark2-es2-mir starts up (which links against libmirclient8), it probes mirclientplatformmesa which loads libmirclient9 (and subsequently libmirprotobuf.so.1) into the same process where libmirclient8 and libmirprotobuf.so.0 are already loaded....gah.
Gah, I guess loading libmirprotobuf.so.0 and libmirprotobuf.so.1 in the same process is more common than I thought since the mirclientplatfo rmmesa module links against libmirclient.
The mako test runner will install the mesa platform modules from the CI build; when glmark2-es2-mir starts up (which links against libmirclient8), it probes mirclientplatfo rmmesa which loads libmirclient9 (and subsequently libmirprotobuf. so.1) into the same process where libmirclient8 and libmirprotobuf.so.0 are already loaded....gah.