Thank you
On Thu, Jan 25, 2024 at 7:09 AM Indan Zupancic wrote:
> Hello Leonid,
>
> On 2024-01-24 21:16, Leonid Meyerovich wrote:
> > I don't have any faults if I use seL4_Recv instead (in a separate
> > thread).
> > It happens only if I use seL4_NBRecv and check the tag after it
> > returns.
Hello Leonid,
On 2024-01-24 21:16, Leonid Meyerovich wrote:
I don't have any faults if I use seL4_Recv instead (in a separate
thread).
It happens only if I use seL4_NBRecv and check the tag after it
returns.
If there is no message or fault pending, seL4_NBRecv() will return
immediately.
W
I don't have any faults if I use seL4_Recv instead (in a separate thread).
It happens only if I use seL4_NBRecv and check the tag after it returns.
I use AARCH64
On Wed, Jan 24, 2024 at 3:59 PM Alwin Joshy wrote:
> Which architecture are you on and are you using the hardware debug API? I
>
On Wed, Jan 24, 2024 at 6:13 PM Leonid Meyerovich wrote:
>
> My root task (root thread created by kernel) checks for fault from the
> other threads, which are created in root thread with badged fault_ep
>
> seL4_Word badge;
> seL4_MessageInfo_t messageInfo = seL4_NBRecv(init_objects.fault_
Which architecture are you on and are you using the hardware debug API? I think
4 is for debug exceptions.
- Alwin
___
Devel mailing list -- devel@sel4.systems
To unsubscribe send an email to devel-leave@sel4.systems
