-
Notifications
You must be signed in to change notification settings - Fork 139
Fix cargo feature 'dump_on_crash' #81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
01523e1
to
9e4a43d
Compare
cba49da
to
9475fd6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM except for that one documentation nit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
12e6bda
to
91a3294
Compare
…ve logic to its own module Signed-off-by: Ludvig Liljenberg <[email protected]>
…bug_assertions Signed-off-by: Ludvig Liljenberg <[email protected]>
…ug" compiles Signed-off-by: Ludvig Liljenberg <[email protected]>
… log::debug, and alias feature with debug_assertions Signed-off-by: Ludvig Liljenberg <[email protected]>
Fixes #70. Renames the feature to just "crashdump". Moves it into VirtualCPU::run, so each driver doesn't need to call it. Behavior should be the same: dumps registers,memory_regions and raw memory to file for certain hyperlightexits: mmio, accessviolation, unknown, and errors.
Also changes uses of
crate::debug!
macro to explicilty use thecrate
module prefix to distinguish from thelog
crate.