On Monday, October 3, 2022 at 10:33:42 PM UTC-5 Ian Lance Taylor wrote:
> > > Am I going to get signal handling problems? Is there anything I can do > with the signal handling to avoid them? > > It's possible. On Linux the dynamic linker may override all the > shared library symbols with the symbols in the main programs. I'm not > sure, and in general it will depend on how the main program is linked. > If it does override, then the duplication of the runtime may not > matter. I'm not really sure, though. > Thank you, Ian. Super helpful as always. To follow up on that intriguing thought about the dynamic linker, how would I tell if the dynamic linker has overridden symbols? Moreover, which flags on the main program would affect this? Lastly, could I clarify one part in the https://pkg.go.dev/os/signal#hdr-Non_Go_programs_that_call_Go_code docs: "For the synchronous signals and SIGPIPE, the Go runtime will install a signal handler. It will save any existing signal handler. If a synchronous signal arrives while executing non-Go code, the Go runtime will invoke the existing signal handler instead of the Go signal handler." Would the two Go runtimes be able to distinguish themselves from each other? The main.go runtime is built as a regular Go program. The c-shared runtime is, well, built under c-shared, so it will have a different stack space and different default signal handling. (I'm thinking of this part of the same os/signal section linked above: "Go code built without -buildmode=c-archive or -buildmode=c-shared will install a signal handler for the asynchronous signals listed above, and save any existing signal handler. If a signal is delivered to a non-Go thread, it will act as described above, except that if there is an existing non-Go signal handler, that handler will be installed before raising the signal.") -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/c60292b5-0469-4993-bb9a-bff6a1576390n%40googlegroups.com.
