Debuginfo tests don't control for ambient tools about rust HOT 9 OPEN

The debuginfo test suite should also be insulated against gdb changing how it prints things, Because It Does.

from rust.

Some points:

• compiletest supports cdb, gdb and lldb, running the test suite for all the ones that are available (either via config.toml or via PATH).
• our LLVM builds do currently not contain lldb.

from rust.

That's... informative, thank you!

It does seem like we should reassess our strategy if we're gonna run a test suite that isn't guaranteed to pass even between different versions of a debugger on "any ol' random debugger lying around".

from rust.

On macOS we can't ship our own debugger. Only an Apple signed lldb is allowed to use the debugging apis of the kernel.

from rust.

Wait, gdb is useless on macOS?

from rust.

Supposedly you can use gdb on macOS jf you sign it with a self-signed code signing certificate which you add to the system keychain, mark as trusted for code signing and set the right entitlements when signing gdb. I don't know if you need to disable SIP for this to work though. We can't disable SIP on CI. https://dev.to/jasonelwood/setup-gdb-on-macos-in-2020-489k

from rust.

Hmm, okay. I think on Linux it is still desirable to control for the sheer amount of variability that Linux distros have, but I can believe that the debuginfo tests have to draw on the environment sometimes.

from rust.

I think it's fine if we can't necessarily control for the debugger used, but we should at least document it and/or report the debugger used when running the debuginfo test suite.

from rust.

yeah, that was also reported as #126628

from rust.