Felix S Klock II

[Visiting for wg-debugging triage](https://rust-lang.zulipchat.com/#narrow/stream/317568-t-compiler.2Fwg-debugging/topic/.5Btriage.20mtg.5D.202022-10-17/near/304471165) Some questions that we had while thinking about this: * What does a debuggable libstd mean? As brson wrote above: It could mean a libstd built...

or actually, maybe this is an instance of a more general problem with type declarations? See e.g. #1623

Also: There is the text that says "Note that the code parameter is `lambda_.Code.from_asset('./my-example-function/out')`", but even there, I don't know what directory that python script will run from. The script...

@rustbot second

From what I can tell, this bug is somehow caused by the use of the 2021 edition in newer projects. If you downgrade to edition=2018, then it will probably resolve...

see also #616

On my end, with a 3990X, the setuid-no-syscallbuf test is failing (and that's the main one that I think I've seen fail with some repeated runs, though sometimes it doesn't...

I assume the trace you want packed is the one in the same `/tmp/rr-test-setuid-XXX` directory; I've put a tarball of that whole directory below. ~~[rr-test-setuid.tar.gz](https://github.com/mozilla/rr/files/5307004/rr-test-setuid.tar.gz)~~ (this wasn't what you asked...

Oh, I'm sorry, you asked me to pack it, and I didn't realized that meant run `rr pack` on it as described in #2694. I'll do that now.

Okay this tar ball has the *packed* version of the directory. [rr-test-setuid.tar.gz](https://github.com/mozilla/rr/files/5307049/rr-test-setuid.tar.gz)