Florian Zwoch

Closing. Actually the next version will have even less special handling cases. It is just too fragile and inconsistent for different use cases. It will be running when set up...

Not sure what restarting the machine should change in addition to closing and starting OBS...

Please re-check with https://github.com/fzwoch/obs-teleport/releases/tag/0.6.0 and re-open if it is still happening.

I have updated the PR to use the latest proposal. It seemed to work fine in my use case - but that may not cover everyone's. @schollz do you have...

Hopefully fixed with GCC 13. I believe the correspondig fix is this one: https://github.com/golang/gofrontend/commit/8db6b78110f84e22c409f334aeaefb80a8b39917 Tested with Debian `gcc-snapshot` `1:20221102-1`.

Looking at it again, I will try to provide a complete repro case: Using the following code: ```go package main //#include //#include import "C" import ( "unsafe" ) var obsModulePointer...

Doing some `dtruss` work for `sigaltstack` ``` 4701/0x5fa3: sigaltstack(0x0, 0x177B56EF0, 0x0) = 0 0 4701/0x5fa3: sigaltstack(0x177B56EB0, 0x0, 0x0) = 0 0 4701/0x5fa4: fork() = 0 0 4701/0x5fa4: sigaltstack(0x0, 0x177BE6EA0, 0x0)...

Small heads-up. I figured my issue seems not to be connected to Go. At some point in OBS simply calling `sigaltstack()` seems to fail with `EPERM`. The reason to that...

You would have to build it yourself at the moment. Maybe I can do a release in the next week or so.

Closed via 1e0d58eba0a223aeea79b18a1a83b86231408726 I had problems applying the PR directly, so I hope I did it right. I think I original misunderstood this: > I am still working on the...