[ Huge cross-post, sorry. Please, only respond to your port list and
debian-www@l.d.o, or at least keep me CC if you drop debian-www ]
Hi ports and ports-like team,
Le 05/04/2012 16:27, David Prévot a écrit :
> The ports and ports-like part of our organization page [1] might be
> pretty outdat
Hi,
I found something about test_socket hang. The problem I'm seeing
looks like a race condition. kdump -H yields:
73334 100505 python CALL thr_kill(0x1884e,SIG(null))
73334 100505 python RET thr_kill 0
73334 100505 python CALL thr_exit(0xccab78)
73334 100430 python CALL thr_ki
Package: gdb
Version: 7.0.1-2+b1
Severity: normal
Tags: patch
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
When debugged process receives signal 32, 33 or 34, gdb prints an error
message without actual signal information:
Program received signal ?, Unknown signal.
This happens because
On Mon, Apr 16, 2012 at 12:58, Robert Millan wrote:
> I'm worried that other packages could begin depending on golang on
> kfreebsd-*, and then it can be a mess if we have to pull it off. But
> I understand your interest in providing it. Please do keep in mind
> that we have very little manpower
Hi Ondřej,
Thanks for forwarding this upstream. It seems to me that it'll be
best to get them involved. It takes either someone with a clear idea
of golang codebase or a complete audit to properly resolve this. And
we don't have time for a complete audit :-(
El 16 d’abril de 2012 10:29, Ondřej
severity 668794 important
forwarded 668794 http://code.google.com/p/go/issues/detail?id=3533
thank you
Hi Robert,
(sorry for BTS juggling, I found your comment just after I sent the
first email.)
Anyway I agree that the problem needs to be fixed upstream, but I would suggest
that we keep GNU/KFr
6 matches
Mail list logo
