@Richard thanks for quick reply, I had tried to repro with the build script you mentioned, but got same results as instructions i followed on the readme. There are 2 interesting points: 1. For ARM build my own compilation and the one i pulled from pypi worked perfectly (all symbol positions were the same). 2. For Intel (64 bit), there is a difference in structs positions between my own compilation and the one i pulled from pypi. For example function "grpc_chttp2_list_pop_writable_stream" offset is different, GRPC metadata presence bits (struct grpc_metadata_batch) are different for some Enums (in particular for grpc_core::HttpPathMetadata), local and remote addresses (offsets) from SocketNode were different.
Like if intel version was compiled either from different source, or patched or used some additional flags when compiled for Pypi upload. Is there anywhere in opensource where i can see the Job that produced the library that was uploaded to Pypi for intel processor ? or any other way to reproduce the exact build ? Thanks in advance. On Friday, September 20, 2024 at 8:41:01 PM UTC+3 Richard Belleville wrote: > This is the script > <https://github.com/grpc/grpc/blob/c6c461bc0ec8ee91c33b6f39f3413fb5ec7bbd3f/tools/run_tests/helper_scripts/build_python.sh> > > used to build the production artifacts in CI for Posix environments. It > should get you all the settings you need to reproduce. > > On Fri, Sep 20, 2024 at 10:03 AM Sasha Solganik <solg...@gmail.com> wrote: > >> Hi Guys, i am trying to implement GRPC monitoring using UBPF for version >> 1.66.1. >> While been sucessfull on ARM, i fail to do so on X86 processors. >> I had tried to to compile cygrpc.cpython-310-x86_64-linux-gnu.so >> according top instructions here: >> https://github.com/grpc/grpc/tree/master/src/python/grpcio >> >> But the resulting SO i get is different from the production one (it is >> with debug symbols and not inlined functions). Also it seems that some >> optimizations are not applied. >> >> My question is how to build cygrpc.cpython exactly the same way as it is >> released to pypi. >> Thanks in advance. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "grpc.io" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to grpc-io+u...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/grpc-io/0b231c19-53ba-4e94-9341-d139761c3388n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/grpc-io/0b231c19-53ba-4e94-9341-d139761c3388n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/c206d822-53f0-4835-88e3-c86e1a591323n%40googlegroups.com.
