On Mon, Jan 15, 2018 at 11:20 PM, Waldek Kozaczuk
wrote:
> Anybody has an idea if this patch is still relevant? None of the golang
> tests I have conducted exposed any issues possibly related to lack of
> arch_prctl SYSCALL.
>
I'm not sure it was ever relevant. Perhaps it was relevant to one Go
Anybody has an idea if this patch is still relevant? None of the golang
tests I have conducted exposed any issues possibly related to lack of
arch_prctl SYSCALL.
On Wednesday, August 31, 2016 at 11:22:37 AM UTC-4, Nadav Har'El wrote:
>
>
> On Wed, Aug 31, 2016 at 4:04 PM, Benoit Canet > wrote:
On Wed, Aug 31, 2016 at 4:04 PM, Benoit Canet <
benoit.canet.cont...@gmail.com> wrote:
> Needed by libraries produced by the Go compiler.
>
> With this patch and the golang app the runtime
> init crash later because of a vdso issue.
>
> It can be examinated by insertion an abort()
> before osv sen
In an earlier review in
https://groups.google.com/forum/#!msg/osv-dev/PW3bkaVCuMg/340vWUeimdMJ
and also today in another thread, I pointed out the problems with this
arch_prctl thing which makes this patch either incomplete or even
counter-productive:
1. After a thread does ARCH_SET_FS, if it get
Needed by libraries produced by the Go compiler.
With this patch and the golang app the runtime
init crash later because of a vdso issue.
It can be examinated by insertion an abort()
before osv send SIGSEGV to the program.
(gdb) bt
at /usr/lib/golang/src/runtime/mheap.go:503
argc=, argv=
