Prev: make package for ports, general question
Next: Possibly unbuildable ports reminder
From: Stanislav Sedov on 26 Feb 2010 18:22
On Sun, 7 Feb 2010 14:06:18 -0500
Ryan Stone <rysto32(a)gmail.com> mentioned:

> I've been trying out valgrind on some threaded FreeBSD applications
> but they've been deadlocking at startup. šI've identified that the
> root cause is that FreeBSD's thread local storage is not being
> emulated properly by valgrind. šThe problem on amd64 is obvious:
> valgrind gives an invalid opcode error when the program tries to
> execute any instruction that accesses the gs register. šOn i386 the
> problem is much more subtle.
>
> I've attached two test applications that demonstrate the problem. šIn
> pthread_self.c, I create one thread which periodically prints
> pthread_self(), and then 10 seconds later I create a second thread.
> After the second thread is created, the first thread believes that it
> is the second thread. šHere's an example invocation:
>

Thank you a lot for the information, I'll try to look into this soon and
will followup in detail.

Sorry for delay in replying.

--
Stanislav Sedov
ST4096-RIPE
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

 | 
Pages: 1
Prev: make package for ports, general question
Next: Possibly unbuildable ports reminder