You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems to work for me, but would be interested in input. I am new to Rust.
unsafe_data points to dynamic_set::Entry, which I then just read as a CString - which seems to work although I thought Rust's strs are not null-terminated.
This is using IntelliJ with the Rust plugin. Then you run a debug session.
Can lldb printing be configured to call native code? If not, I’m afraid there’s no way around duplicating in python many implementation details of the library that can change in any future version
Activity
vjpr commentedon Sep 2, 2021
Work is ongoing here intellij-rust/intellij-rust#3000
vjpr commentedon Sep 6, 2021
I actually will need help with this.
Is there a way to get the string from the
unsafe_dataptr?vjpr commentedon Sep 7, 2021
This seems to work for me, but would be interested in input. I am new to Rust.
unsafe_datapoints todynamic_set::Entry, which I then just read as a CString - which seems to work although I thought Rust'sstrs are not null-terminated.This is using IntelliJ with the Rust plugin. Then you run a debug session.
~/.lldbinit
lldb_init.py
summaries.py
SimonSapin commentedon Aug 20, 2026
Can lldb printing be configured to call native code? If not, I’m afraid there’s no way around duplicating in python many implementation details of the library that can change in any future version