On Fri, May 6, 2011 at 6:47 PM, Ryan Stone wrote:
> On Wed, Apr 27, 2011 at 3:28 PM, Ryan Stone wrote:
>> (Sorry for the noise earlier about the PBIs not working under PC-BSD;
>> I'm not sure how I missed that had been already reported).
>>
>> I tried th
On Wed, Apr 27, 2011 at 3:28 PM, Ryan Stone wrote:
> (Sorry for the noise earlier about the PBIs not working under PC-BSD;
> I'm not sure how I missed that had been already reported).
>
> I tried the new amd64 PBI and I am able to successfully start VMs now.
> I had
(Sorry for the noise earlier about the PBIs not working under PC-BSD;
I'm not sure how I missed that had been already reported).
I tried the new amd64 PBI and I am able to successfully start VMs now.
I had one VM(running some relatively recent version of amd64 HEAD)
boot up fine, but a second one
On Sun, Apr 24, 2011 at 8:02 AM, Bernhard Froehlich wrote:
> On Fri, 22 Apr 2011 13:01:40 +0200, Bernhard Froehlich wrote:
>> PBIs for PC-BSD are currently worked on and will hopefully be available
>> in a few days.
>
> Thanks a lot to Jesse Smith, Dru Lavigne and Ken Moore for the efforts
> to pr
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 err
