Sean Cross

I don't think hardware exposes a network port, unless you're talking about the gdb server presented by `wishbone-util` which I don't think has been used in ages, in which case...

`3333` is useful for when Xous itself has crashed, or when you're debugging the bootloader and Xous isn't even running. It's a stop-the-world debugger. Like "God Mode" on the Vex,...

It should be noted that `3333` has no concept of processes or threads. You can single-step, and you can insert an unlimited number of breakpoints, but it's somewhat arbitrary what...

I have an `unwinding` version in the works. This may be useful. Unfortunately, while it gives you a stack trace, it does not give you symbol names. So you'd get...

It doesn't NAT packets, yeah. Getting it online is still somewhat manual: 1. Create an interface with Renode. If you run `xous-release-tap.resc` then this will create an actual interface you...

With https://github.com/betrusted-io/rust/commit/c9a00020835b613ad4eff578662282b80b30b7a2 we now have the ability to destroy keys on Xous. This code comes from a libstd rework, and has been backported to the patchset that we've been carrying...

For the record, this is the `unset` function in question: ```rust pub fn unset(&mut self, key: &str) -> Result { // log::info!("unset '{}'", key); let mut keypath = PathBuf::new(); keypath.push(MTXCLI_DICT);...

I'm actually not able to reproduce this:  There were some changes to std::fs to implement lstat and friends, but that wouldn't have affected this: https://github.com/betrusted-io/rust/commit/452f331576874ea6c216d3626a453f399356ad52 Can you give steps...

I'm still not able to replicate it 

An alternative is to make `CID` (or is it `Connection`?) an explicit type that doesn't implement `Copy` or `Clone`. That way you can't copy connection IDs. Then we wrap them...