Cargo test panics with no backtrace

1

I can't run cargo test on one of my projects:

     Running unittests src/lib.rs (/home/*/target/debug/deps/*-29db5e9c78b698aa)
thread panicked while processing panic. aborting.
error: test failed, to rerun pass `--lib`

Caused by:
  process didn't exit successfully: `/home/*/target/debug/deps/*-29db5e9c78b698aa` (signal: 6, SIGABRT: process abort signal)

This is all I get, regardless of the RUST_BACKTRACE's values I specify. I have no idea what that might be. Where to start digging?

2

Okay, figured that one out. Just run the process didn't exit successfully process in a debugger and you'll get the stack trace.

3

This probably means that you have something like panicking Drop implementation. Could you bisect the problem to a single test, for example?

4

It was a failing global allocator that was panicking in "alloc". Also, it was not related to the testing code at all, it was the Rust prologue (the runtime setting up stage).

5

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.