Help with completing internal rust test script

Hello,

So I’m trying to finish up my first pr in the rust-lang repo and am encountering an errors in the ‘debuginfo’ test suite when I run ‘python x.py test’. I don’t really know what I’m looking at am wondering if you all can help with a probably really easy fix.

Trace …


Debugger commands script is '/path/to/rust/build/x86_64-apple-darwin/test/debuginfo/vec-slices/vec-slices.debugger.script'.
Target executable is '/path/to/rust/build/x86_64-apple-darwin/test/debuginfo/vec-slices/a'.
Current working directory is '/path/to/rust'
Creating a target for '/path/to/rust/build/x86_64-apple-darwin/test/debuginfo/vec-slices/a'
settings set auto-confirm true

version
lldb version 7.0.0
command script import /path/to/rust/./src/etc/lldb_rust_formatters.py
type summary add --no-value --python-function lldb_rust_formatters.print_val -x ".*" --category Rust
type category enable Rust

breakpoint set --file 'vec-slices.rs' --line 132
Breakpoint 1: where = a`main + 281 at vec-slices.rs:132, address = 0x0000000100001ac9
run
error: shell expansion failed (reason: could not get support executable directory for lldb-argdumper tool). consider launching with 'process launch'.

print empty
error: Multiple internal symbols found for 'empty'
id = {0x000002d6}, range = [0x00000000000950b4-0x00000000000950b8), name="empty"
id = {0x000002d1}, range = [0x0000000000095090-0x0000000000095098), name="empty"
id = {0x000002d3}, range = [0x00000000000950a0-0x00000000000950a8), name="empty"

error: use of undeclared identifier 'empty'

print singleton
error: use of undeclared identifier 'singleton'

print multiple
error: use of undeclared identifier 'multiple'

print slice_of_slice
error: use of undeclared identifier 'slice_of_slice'

print padded_tuple
error: use of undeclared identifier 'padded_tuple'

print padded_struct
error: use of undeclared identifier 'padded_struct'

quit
None

------------------------------------------
stderr:
------------------------------------------

------------------------------------------

thread '[debuginfo-lldb] debuginfo/vec-slices.rs' panicked at 'explicit panic', tools/compiletest/src/runtest.rs:3196:9

---- [debuginfo-lldb] debuginfo/vec.rs stdout ----
NOTE: compiletest does not know which version of LLDB it is using

error: line not found in debugger output: [...]$0 = [1, 2, 3]
status: exit code: 0

And then the tests all seem to fail with this error. I can’t seem to figure out what ‘process launch’ means and have no idea why compiletest can’t find the of version of lldb. Is this a common thing? Is something wrong with my environment?

Thanks in advance for any help

  • Matt