Le 21/04/12 19:47, Christoph Egger a écrit :
>> rip 0x0 and rsp 0x50202 look really abnormal to me. I'll have a look in
>> FreeBSD, that's probably a group of exceptions that have to be handled
>> differently.
>
> rip 0x0 often means that a function pointer has been called which is
NULL.
>
> Chr
On 21.04.12 19:38, Jean-Yves Migeon wrote:
> Le 21/04/12 16:31, Jean-Yves Migeon a écrit :
>>> Okay, thanks for the report. So this rules out Virtual Box, it seems to
>>> happen on native amd64 too.
>>>
>>> I am taking a look right now.
>>
>> This seems to be a bug in the trap handling code. The si
Le 21/04/12 16:31, Jean-Yves Migeon a écrit :
Okay, thanks for the report. So this rules out Virtual Box, it seems to
happen on native amd64 too.
I am taking a look right now.
This seems to be a bug in the trap handling code. The signal is caught
correctly (it reaches T_ALIGNFLT|T_USER in trap
Le 21/04/12 14:50, Jean-Yves Migeon a écrit :
The machine did not drop into ddb, it simply rebooted. Unfortunately
it did not leave a core dump behind, so I don't have much to look at
just yet. When I get home later today, I will try to get more info.
BTW, this occurred while running the ATF tes
On Fri, 20 Apr 2012 15:33:05 -0700 (PDT), Paul Goyette wrote:
On Fri, 20 Apr 2012, Paul Goyette wrote:
XXX I would appreciate if someone could test it under a real amd64
host with an up-to-date kernel, so I can reasonably assume that the
culprit is Virtual Box and not our amd64 port (my test m
On Fri, 20 Apr 2012, Paul Goyette wrote:
The machine did not drop into ddb, it simply rebooted. Unfortunately it did
not leave a core dump behind, so I don't have much to look at just yet. When
I get home later today, I will try to get more info.
BTW, this occurred while running the ATF tes
On Fri, 20 Apr 2012, Paul Goyette wrote:
XXX I would appreciate if someone could test it under a real amd64 host
with an up-to-date kernel, so I can reasonably assume that the culprit is
Virtual Box and not our amd64 port (my test machine being off line I cannot
do it myself). Results from oth
XXX I would appreciate if someone could test it under a real amd64
host with an up-to-date kernel, so I can reasonably assume that the
culprit is Virtual Box and not our amd64 port (my test machine being
off line I cannot do it myself). Results from other arches would be a
plus too.
I just up
