I've done both of those, neither worked because the memory wasn't accessible
when setting the breakpoint and it doesn't let you single step over an sret.
------- Original Message -------
On Monday, July 11th, 2022 at 9:39 AM, Sid Agrawal <siag...@cs.ubc.ca> wrote:
>
>
> Re. Breakpoint in user mode. This might be a silly thing but it did trip me
> up so worth pointing out. While running gdb, ensure that you are loading
> the symbols for the user task and not the kernel.
>
> Window1:
> ./simulate --extra-qemu-args="-S -s"
>
>
> Window2:
> ${CROSS_COMPILER_PREFIX}gdb
> projects/sel4test/apps/sel4test-driver/sel4test-driver
> (inside gdb) target remote :1234
> (inside gdb) b <some func in your root task>
>
>
> src: https://docs.sel4.systems/projects/sel4-tutorials/debugging-guide
>
> -Sid
>
>
> On Mon., Jul. 11, 2022, 1:28 a.m. Ahmed Charles, m...@ahmedcharles.com
>
> wrote:
>
> > On one of my computers:
> >
> > QEMU emulator version 7.0.0 (Debian 1:7.0+dfsg-2~bpo11+2)
> > Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
> >
> > $ ../init-build.sh -DPLATFORM=spike -DRISCV64=TRUE -DRELEASE=FALSE
> > -DSIMULATION=TRUE
> > $ ninja
> > $ ./simulate -m 1G # becomes: qemu-system-riscv64 -machine spike -cpu rv64
> > -nographic -serial mon:stdio -m size=1G -bios none -kernel
> > images/sel4test-driver-image-riscv-spike
> >
> > Thanks
> >
> > ------- Original Message -------
> > On Monday, July 11th, 2022 at 1:13 AM, Ivan Velickovic <
> > i.velicko...@unsw.edu.au> wrote:
> >
> > > What platform are you trying to build for sel4test? What command did you
> > > use to build sel4test? QEMU version 6.0.0 works successfully for me.
> > >
> > > > On 11/07/2022, at 3:43 PM, Ahmed Charles m...@ahmedcharles.com wrote:
> > > >
> > > > I'm having similar issues getting seL4test to work on riscv32/64 on
> > > > QEMU 6.0.0 and 7.0.0. I tried debugging with a connected gdb, but I'm
> > > > new
> > > > at this and setting breakpoints in user mode seems to fail, so I'm not
> > > > sure
> > > > what happens once the root task starts, other than it eventually runs an
> > > > infinite loop (0: j 0b, specifically).
> > > >
> > > > Any ideas? Thanks.
> > > > _______________________________________________
> > > > Devel mailing list -- devel@sel4.systems
> > > > To unsubscribe send an email to devel-leave@sel4.systems
> > > > _______________________________________________
> > > > Devel mailing list -- devel@sel4.systems
> > > > To unsubscribe send an email to devel-leave@sel4.systems
>
> _______________________________________________
> Devel mailing list -- devel@sel4.systems
> To unsubscribe send an email to devel-leave@sel4.systems
_______________________________________________
Devel mailing list -- devel@sel4.systems
To unsubscribe send an email to devel-leave@sel4.systems
