Erik Kaneda

Here are several code changes that we've added in our tests which are likely due to nondeterministic binaries: https://github.com/risc0/risc0/pull/553/files#diff-46a860afd43fe55f5e7442917718a4a5357fb4a76b2169d98c8c885158af8e2dR467 The `% 1094` was added because the different instructions could be...

I've been looking at issues on github about reproducible builds and I wanted to add some observations... When I build multitest on different commits, I get different values for `MULTI_TEST_ELF.len()`...

I think this can pose a chicken and egg problem but I'm not exactly sure... I'll write down my thoughts... The MethodID of a given guest method can be thought...

Oh from reading @intoverflow's proposed fix, we can write the set of method ID's after the load phase, meaning that the initialization of the read only memory region wouldn't be...

Another point: given an execution trace and a set of method ID's, how do we know that the correct method ID's were loaded to a read only memory region? I...

[This](https://github.com/risc0/risc0/tree/gdb-stub) branch contains an attempt to use the `gdb-stub` library. It's best to hold off on this until parts of preflight and/or continuations are implemented

@weikengchen thanks for your work! I tried implementing this a few months ago and encountered an error in gdbstub saying that it got an error from the version of gdb...

I can't reproduce this on my end using the current head of the risc0 repo. I'm doing `cargo build -p risc0-zkvm` and it runs without displaying this error

we updated to 1.74 today. Does this still persist on your end?

So I'm looking at this run and https://github.com/risc0/risc0/pull/1483 and I'm not seeing a huge difference in execution time but it makes the Cargo.toml's look cleaner, which is nice