rust 如何在广发银行调试一个失败的cargo测试?

qltillow  于 2022-12-23  发布在  Go
关注(0)|答案(2)|浏览(184)

我的货物测试失败:

$ cargo test
[snip]
    Running target/gunzip-c62d8688496249d8

running 2 tests
test test_extract_failure ... FAILED
test test_extract_success ... ok

failures:

---- test_extract_failure stdout ----
        task 'test_extract_failure' panicked at 'assertion failed: result.is_err()', /home/dhardy/other/flate2-rs/tests/gunzip.rs:19


failures:
    test_extract_failure

test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured

task '<main>' panicked at 'Some tests failed', /home/rustbuild/src/rust-buildbot/slave/nightly-linux/build/src/libtest/lib.rs:250

如何在像GDB这样的调试器中启动失败的测试?
这应该是一个一般性的问题,但对于那些想要追溯我的步骤,安装最近的每夜 rust 构建和:

git clone https://github.com/dhardy/flate2-rs.git
git checkout 24979640a880
cd flate2-rs
cargo test
puruo6ea

puruo6ea1#

您可以通过向测试二进制文件传递附加参数来获取它以筛选它运行的测试; Cargo也直接暴露了这个,因此cargo test test_extract_failure只会运行那个特定的用例(如果您有其他测试出现异常并且预期会失败,这样它们就不会调用我将要提到的rust_panic函数,而只会在那里留下令人不快的调用,那么这就很方便了)。
为了使用gdb,你需要直接运行测试二进制文件(如果你使用Cargo,它在一个子进程中运行,因此gdb不会捕捉到它内部的异常)。Cargo告诉你文件名target/gunzip-c62d8688496249d8。你可以直接用--test运行它,使之成为一个测试运行:

$ target/gunzip-c62d8688496249d8 --test test_extract_failure
running 1 test
test test_extract_failure ... FAILED

failures:

---- test_extract_failure stdout ----
        task 'test_extract_failure' panicked at 'assertion failed: result.is_err()', /home/dhardy/other/flate2-rs/tests/gunzip.rs:19


failures:
    test_extract_failure

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured

task '<main>' panicked at 'Some tests failed', /home/rustbuild/src/rust-buildbot/slave/nightly-linux/build/src/libtest/lib.rs:250

现在把它和gdb连接起来,有一个很方便的函数rust_panic,你可以为它插入一个断点,一旦进入gdb,break rust_panic就意味着在实际展开之前,每当有什么东西触发了恐慌,它就会暂停。
以下是一个会话可能会出现的结果:

$ gdb target/demo-92d91e26f6ebc557
…
Reading symbols from target/demo-92d91e26f6ebc557...done.
(gdb) break rust_panic
Breakpoint 1 at 0xccb60
(gdb) run --test test_extract_failure
Starting program: /tmp/demo/target/demo-92d91e26f6ebc557 --test test_extract_failure
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

running 1 test
[New Thread 0x7ffff6ef4700 (LWP 14254)]
[New Thread 0x7ffff5fff700 (LWP 14255)]
[Switching to Thread 0x7ffff5fff700 (LWP 14255)]

Breakpoint 1, 0x0000555555620b60 in rust_panic ()
(gdb) bt
#0  0x0000555555620b60 in rust_panic ()
#1  0x0000555555621274 in unwind::begin_unwind_inner::hb821324209c8ed246Qc ()
#2  0x000055555556bb6d in unwind::begin_unwind::h7834652822578025936 ()
#3  0x000055555556b9fd in demo::do_something () at <std macros>:8
#4  0x000055555556b98e in demo::test_extract_failure () at src/lib.rs:3
#5  0x000055555559aa4b in task::TaskBuilder::try_future::closure.8077 ()
#6  0x000055555560fd03 in task::TaskBuilder::spawn_internal::closure.30919 ()
#7  0x000055555561f672 in task::Task::spawn::closure.5759 ()
#8  0x0000555555621cac in rust_try_inner ()
#9  0x0000555555621c96 in rust_try ()
#10 0x000055555561f713 in unwind::try::ha8078a6ae9b50ccepFc ()
#11 0x000055555561f51c in task::Task::run::hdb5fabf381084abafOb ()
#12 0x000055555561f168 in task::Task::spawn::closure.5735 ()
#13 0x0000555555620595 in thread::thread_start::h4d73784c295273b3i6b ()
#14 0x00007ffff79c2314 in start_thread () from /usr/lib/libpthread.so.0
#15 0x00007ffff72e25bd in clone () from /usr/lib/libc.so.6
(gdb)

在该特定情况下,#0-#2和#5-#15是噪声,#3和#4是我们需要的信号。

brgchamk

brgchamk2#

cargo build现在有一个参数

--test [<NAME>]           Build only the specified test target

其构建仅具有作为参数提供的测试集的二进制文件。

相关问题