On 30/08/11 at 21:08 +0200, Petr Salinger wrote:
Could you try make test-all ? While some failures and errors are
expected, it stresses the interpreter a bit more, so it's a good way to
check that it doesn't block.
Under sid, it fails to start, probably due to
multiarch changes of libc
So, I don't know what to do.
How likely are those problems to be fixed in kfreebsd?
The needed primitives [1] for pthread add-on rewrite
should be available and working in FreeBSD 9.0 kernel.
The 8.x have only limited support.
No ETA for eglibc rewrite now ;-)
Petr
[1]
On 31/08/11 at 11:37 +0200, Petr Salinger wrote:
So, I don't know what to do.
How likely are those problems to be fixed in kfreebsd?
The needed primitives [1] for pthread add-on rewrite
should be available and working in FreeBSD 9.0 kernel.
The 8.x have only limited support.
No ETA for
Would you have time to turn that into a (tested ;) ) patch?
With attached patch on top of 1.9.3~preview1+svn33077-3
make test
#244 test_fork.rb:51:in `top (required)':
a = []
trap(:INT) { a.push(1) }
trap(:TERM) { a.push(2) }
pid = $$
begin
fork do
On 30/08/11 at 13:52 +0200, Petr Salinger wrote:
Would you have time to turn that into a (tested ;) ) patch?
With attached patch on top of 1.9.3~preview1+svn33077-3
make test
Thanks!
Could you try make test-all ? While some failures and errors are
expected, it stresses the interpreter a
Could you try this version:
---
a = []
trap(:INT) { puts INT recvd ; a.push(1) }
trap(:TERM) { puts TERM recvd ; a.push(2) }
pid = $$
puts parent pid: #{pid}
begin
fork do
puts child pid: #{$$}
sleep 0.5
Process.kill(:INT, pid)
Process.kill(:TERM, pid)
puts signals sent.
end
On 30/08/11 at 20:18 +0200, Petr Salinger wrote:
Could you try this version:
---
a = []
trap(:INT) { puts INT recvd ; a.push(1) }
trap(:TERM) { puts TERM recvd ; a.push(2) }
pid = $$
puts parent pid: #{pid}
begin
fork do
puts child pid: #{$$}
sleep 0.5
Process.kill(:INT, pid)
Could you try make test-all ? While some failures and errors are
expected, it stresses the interpreter a bit more, so it's a good way to
check that it doesn't block.
Under sid, it fails to start, probably due to
multiarch changes of libc location:
8 matches
Mail list logo
