On 10 April 2018 at 09:16, Ajay Garg wrote:
> On Tue, Apr 10, 2018 at 1:08 PM, Peter Maydell
> wrote:
>> What hardware (what CPU, board, etc) is this "rumprun" software
>> expecting to run on?
>
> Yep, just to ensure that there are no cross-compiling issues, I am
> building rumprun on the pseudo
On 10 April 2018 at 05:14, Ajay Garg wrote:
> Thanks Alex for the reply ..
>
>>
>> Can you run under -s -S and gdb step the *guest* and see where it ends
>> up. The above error is usually indicative of the guest going off into
>> the weeds somewhere because the hardware isn't what it expects.
>>
>
Thanks Peter .. my sincere gratitude.
You pin-pointed the real issue ..
On Tue, Apr 10, 2018 at 2:50 PM, Peter Maydell wrote:
> On 10 April 2018 at 09:16, Ajay Garg wrote:
>> On Tue, Apr 10, 2018 at 1:08 PM, Peter Maydell
>> wrote:
>>> What hardware (what CPU, board, etc) is this "rumprun" s
Hi Peter.
Thanks for the reply.
On Tue, Apr 10, 2018 at 1:08 PM, Peter Maydell wrote:
> On 10 April 2018 at 05:14, Ajay Garg wrote:
>> Thanks Alex for the reply ..
>>
>>>
>>> Can you run under -s -S and gdb step the *guest* and see where it ends
>>> up. The above error is usually indicative of