2010/4/21 Blue Swirl :
> On 4/21/10, Artyom Tarasenko wrote:
>> 2010/4/16 Artyom Tarasenko :
>>
>> > 2010/4/15 Artyom Tarasenko :
>> >> 2010/4/15 Blue Swirl :
>> >>> On 4/15/10, Artyom Tarasenko wrote:
>> 2010/4/15 Artyom Tarasenko :
>>
>> > One of LX's tests crashes pretty ha
On 4/21/10, Artyom Tarasenko wrote:
> 2010/4/16 Artyom Tarasenko :
>
> > 2010/4/15 Artyom Tarasenko :
> >> 2010/4/15 Blue Swirl :
> >>> On 4/15/10, Artyom Tarasenko wrote:
> 2010/4/15 Artyom Tarasenko :
>
> > One of LX's tests crashes pretty hard, causing qemu abort.
>
2010/4/16 Artyom Tarasenko :
> 2010/4/15 Artyom Tarasenko :
>> 2010/4/15 Blue Swirl :
>>> On 4/15/10, Artyom Tarasenko wrote:
2010/4/15 Artyom Tarasenko :
> One of LX's tests crashes pretty hard, causing qemu abort.
> I've tried to look how does the execution flow works with -
2010/4/15 Artyom Tarasenko :
> 2010/4/15 Blue Swirl :
>> On 4/15/10, Artyom Tarasenko wrote:
>>> 2010/4/15 Artyom Tarasenko :
>>>
>>> > One of LX's tests crashes pretty hard, causing qemu abort.
>>> > I've tried to look how does the execution flow works with -d in_asm.
>>> > Does the address in
2010/4/15 Artyom Tarasenko :
> One of LX's tests crashes pretty hard, causing qemu abort.
> I've tried to look how does the execution flow works with -d in_asm.
> Does the address in the log show the guest's PC register?
It's probably sort of a "timing" issue.
Can we check exceptions not just on
2010/4/15 Blue Swirl :
> On 4/15/10, Artyom Tarasenko wrote:
>> 2010/4/15 Artyom Tarasenko :
>>
>> > One of LX's tests crashes pretty hard, causing qemu abort.
>> > I've tried to look how does the execution flow works with -d in_asm.
>> > Does the address in the log show the guest's PC register?
On 4/15/10, Artyom Tarasenko wrote:
> 2010/4/15 Artyom Tarasenko :
>
> > One of LX's tests crashes pretty hard, causing qemu abort.
> > I've tried to look how does the execution flow works with -d in_asm.
> > Does the address in the log show the guest's PC register?
>
>
> It's probably sort of a
