| /openbsd/sys/arch/arm/arm/ |
| H A D | sigcode.S | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|
| /openbsd/sys/arch/riscv64/riscv64/ |
| H A D | locore.S | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|
| /openbsd/sys/arch/sh/sh/ |
| H A D | locore_subr.S | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|
| /openbsd/sys/arch/m88k/m88k/ |
| H A D | subr.S | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|
| /openbsd/sys/arch/mips64/mips64/ |
| H A D | lcore_access.S | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|
| /openbsd/sys/arch/powerpc64/powerpc64/ |
| H A D | locore.S | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|
| /openbsd/sys/arch/arm64/arm64/ |
| H A D | locore.S | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|
| /openbsd/sys/arch/macppc/macppc/ |
| H A D | locore.S | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|
| /openbsd/sys/arch/hppa/hppa/ |
| H A D | locore.S | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|
| /openbsd/sys/arch/amd64/amd64/ |
| H A D | locore.S | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|
| /openbsd/sys/arch/sparc64/sparc64/ |
| H A D | locore.s | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|
| /openbsd/sys/arch/i386/i386/ |
| H A D | locore.s | d8417bd7 Tue Dec 12 07:37:20 GMT 2023 deraadt <deraadt@openbsd.org> The sigtramp was calling sigreturn(2), and upon failure exit(2), which
doesn't make sense anymore. It is better to just issue an illegal
instruction.
ok kettenis, with some misgivings about inconsistant approaches between
architectures.
In the future we could change sigreturn(2) to never return an exit code,
but always just terminate the process. We stopped this system call
from being callable ages ago with msyscall(2), and there is no stub for
it in libc.. maybe that's the next step to take?
|