Some promising ideas…bpf-direct.c - samples/seccomp/bpf-direct.c - Linux source code v6.10.6 - Bootlinelixir.bootlin.comIf we can get the seccomp filter installed and identify where the Go code is beforehand (may be possible by placing two objects before and after a c-archive such that symbol value
Hi all
I ran into this error with generic types. Here is the sample program
below, which is my best effort to boil it down to its simplest expression.
I can build and run the program fine with go 1.23.0. However, on line 15
vscode reports the error I put in the comment on that line. I do not kn
Thanks, I'll rediscuss the risk with my team, maybe we can live with it.
Btw, I prefer RegisterName, as long as we register in init, the program
will crush immediately for a dup. On the other hand, Register exposes us to
refactoring a type's name or to moving a type from package A to package B,
On Sat, Aug 24, 2024 at 2:51 AM gavraz wrote:
>
> 1. I attempted to wrap gob with my own package and specify a distinct
> toolchain, hoping it would result in a fully independent copy of the gob
> package in the compiled code. Thanks for the clarification, this approach is
> a no-go.
> 2. The c
[Thank you for taking the time to answer my questions, very much
appreciated.]
1. I attempted to wrap gob with my own package and specify a distinct
toolchain, hoping it would result in a fully independent copy of the gob
package in the compiled code. Thanks for the clarification, this approach
