[Gedare Bloom]

Youren Shen,

It looks like the problem you are having is that RTEMS "hello world"
executes a sensitive instruction? There should not be any such
instruction when you use the --enable-paravirt option, so you need to
determine where this instruction gets executed. The best way to do
this is to hook gdb up to an executing qemu. You can start qemu with
some -S option to prevent the boot sequence from starting to give you
some time to load gdb and connect it to qemu's gdbserver socket. once
you have done this, you should be able to set some breakpoints in the
pok/hello application to step through the program, or you might be
able to catch exceptions before they get raised to pok. The other
option should be that inside pok there should be some information
about the source of the exception that you might investigate.

Please keep us informed about your progress on this problem,
Thanks,
Gedare

On Thu, Mar 20, 2014 at 9:16 AM, Youren Shen <shenyouren at gmail.com> wrote:
> Hi,Gedare
>
> Maybe it's because my qemu version is low or POK has change the kernel, I
> can't run the RTEMS Hello world on my computer anymore.
>
> The problem has spent me a few days to find. More details see this mails.
>
> [1].
> http://listengine.tuxfamily.org/lists.tuxfamily.org/pok/2014/03/msg00000.html
>
> -----
> Best Regards.
> Youren Shen.
>
>
> On Thu, Mar 20, 2014 at 8:03 PM, Philipp Eppelt
> <philipp.eppelt at mailbox.tu-dresden.de> wrote:
>>
>> On 03/16/2014 01:01 PM, Youren Shen wrote:
>> > Hi, every one:
>> >
>> > I have write a blog about how to build the RTEMS on POK. However, the
>> > RTEMS can't run on POK now. Here is my blog[1].
>> >
>> > [1].
>> > http://huaiyusched.github.io/rtems/2014/03/15/how-to-run-rtems-on-pok/
>> > --
>> > Best Regards.
>> > Youren Shen.
>>
>>
>> Hi Youren,
>>
>> great!
>> A screenshot of RTEMS HelloWorld sample running on POK would be even
>> better :).
>>
>> Cheers,
>> Philipp
>
>
>
>
> --
> Best Regards.
> Youren Shen.