JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.
USoC22 - Debugging - Snapshot Assessment
Assess understanding of third session
Sign in to Google
to save your progress.
Learn more
* Indicates required question
For what platform can we debug an Unikraft image in the same way we debug a common executable?
*
1 point
KVM
Linuxu
Xen
What is the library that provides tracepoints in Unikraft?
*
1 point
uktrace
ukdebug
ukpoint
ukstore
What is part of the GDB debugging process for KVM? (Select all the correct answers)
*
1 point
Running the image using GDB
Running the image in the paused state
Connecting to the image with GDB on the 1234 port
Running the image as a normal executable
Using hardware breakpoints
Required
What repository provides the python script for parsing and reporting data from a trace file?
*
1 point
The Unikraft core repository
Every application repository
The ukdebug external library repository
The uktrace external library repository
What should be done in order to instrument Unikraft using tracepoints? (Select all the correct answers)
*
1 point
Include `uk/trace.h` in the instrumented source files
Avoid connecting with GDB to the running image
Register all tracepoints handlers using UK_TRACEPOINT
Use the verbose build option `make V=1`
Call the generated tracepoint handlers
Enable ukdebug
Required
Submit
Clear form
This content is neither created nor endorsed by Google.
Report Abuse
-
Terms of Service
-
Privacy Policy
Forms
