JackN

@TheButlah Are you able to validate https://github.com/probe-rs/probe-rs/pull/1327. I can no longer reproduce the problem on my own repo, or the one you linked above.

Breakpoints and stepping will be an onion that we have to continue to peel one layer at a time ... with maybe some specific requests for improvements on the DWARF...

@t-moe and @bugadani : This is partially my fault for not looking at this PR sooner, but renaming that option breaks the VSCode plugin. Will it cause conflicts with cargo...

Clap doesn't use serde, but those structs are shared for deserializing plugin options. I'm 100% in agreement with updating the plugin, but there i always that awkward gap for people...

Totally agree. I think when we move from a `0.xxx` to a `1.xxx` might be a good time. It will feel weird to have a MarketPlace release for a `0.24`...

@Tiwalun and @Yatekii : While reviewing and testing #2134, I uncovered a 'logical' gap in the cargo tests that rely on pre-generated binaries. For instance, Rust compiler recently started using...

Great discussion. FYI, for the `dap-server` and VSCode extension, I added a user config to select core [0-n], with a default of 0. This is used during attach, and will...

My knowledge of this part of RISC-V is superficial, but would it make sense to have a "core to tap" mapping in the target definition, similar to the way we...

> Do you think we can land this PR as is? I see that only the main idea isn't checked off yet, but if the changes stand on their own...

> Do you think we can land this PR as is? I see that only the main idea isn't checked off yet, but if the changes stand on their own...