Can someone provide more information about using seL4_DebugSnapshot?
From its description in documentation, I would expect it to print out a CapDL struct over a debugging port/console. Instead, it waits for user commands for various data types sends back binary data[0].
Since the commands are all 0xa0-0xff[1], it doesn't seem like DebugSnapshot expects a human and a keyboard to be present on the other end. Is there some internal debugging tool that is supposed to be used with this system call? Is DebugSnapshot still used? Any advice or information is appreciated. ras [0] https://github.com/seL4/seL4/blob/master/src/arch/arm/32/machine/capdl.c [1] https://github.com/seL4/seL4/blob/master/include/machine/capdl.h
Can someone provide more information about using seL4_DebugSnapshot? From its description in documentation, I would expect it to print out a CapDL struct over a debugging port/console. Instead, it waits for user commands for various data types sends back binary data[0].
Since the commands are all 0xa0-0xff[1], it doesn't seem like DebugSnapshot expects a human and a keyboard to be present on the other end. Is there some internal debugging tool that is supposed to be used with this system call? Is DebugSnapshot still used? Any advice or information is appreciated. This debug feature isn't currently maintained and not well supported. There was an internal tool that interacted with DebugSnapshot to translate the binary data into a human readable format but hasn't been updated until recently and is still not functional enough for release. At present it is better to assume DebugSnapshot is unsupported sorry.
ras
[0] https://github.com/seL4/seL4/blob/master/src/arch/arm/32/machine/capdl.c
[1] https://github.com/seL4/seL4/blob/master/include/machine/capdl.h
participants (2)
-
Mcleod, Kent (Data61, Kensington NSW)
-
rasd@riseup.net