-
Notifications
You must be signed in to change notification settings - Fork 6
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
hermit-sys
, with features: instrument
but hermit-sys
does not have these features
#2
Comments
I have not published the crate to crates.io yet, so it had to be commented out from hermit-sys cargo file. The Readme is slightly out of date, the last commits changed some things. Have to revise it and publish it. Take a look at the basic example to see the current "userland" interface. In hermit-sys you have to use the backend with autokernel and interruptsafe features afaik |
hermit-os/hermit-rs#55 should resolve the issue |
Thanks 😄 I'll give it a try after it was merged. |
It took me a while to get back to this, but I finally found some time. Trace generation seems to be working, but the symbol table generated by nm is missing the offset that is used by hermitcore. I had to run something like |
I've not been following hermit's development lately, but I guess this is related to the changes to kernel relocation (hermit-os/loader#8). For the purposes of mapping addresses to functions, uftrace treats all in-memory binaries as relocatable, and uses the
I am not sure if there is a nice, general fix for this issue. The file is generated by the rftrace-frontend. When using I suppose I could just change the offset in rftrace (as rustyhermit is the only usecase for non-linux mode right now), though that seems a bit dirty. |
Related: hermit-os/hermit-rs#147 |
This is now resolved as of #32. 🥳 |
I wanted to try your traces with the demo application of the rusty-hermit repo, however I get the error messaged name in title. Here is what I did:
git clone --recursive https://github.com/hermitcore/rusty-hermit.git
rust-toolchain
file and set it to nightlycargo build -Z build-std=std,core,alloc,panic_abort --target x86_64-unknown-hermit
worked fine and I could run the demo with uhyvedemo/Cargo.toml
:If I call
cargo build -Z build-std=std,core,alloc,panic_abort,instrument-mcount --target x86_64-unknown-hermit --release
I get the following output:Do you have an idea why it is not working for me?
The text was updated successfully, but these errors were encountered: