Codebase list rust-libslirp / e4d0e3d
describe how to enable proper stack traces Ximin Luo 4 years ago
1 changed file(s) with 10 addition(s) and 0 deletion(s). Raw diff Collapse all Expand all
+10
-0
README.rst less more
270270 and add both the ``Cargo.toml`` and the source code changes to it. The change
271271 to ``Cargo.toml`` would then simply say (e.g.) ``0.5`` since the older versions
272272 actually don't work, and not the version range from the previous paragraph.
273
274 Help, something went wrong!
275 ---------------------------
276
277 Sometimes, the error messages are not the most informative. In this case you
278 can try re-running the command with ``RUST_BACKTRACE=1``. If you are using the
279 ``debcargo`` from Debian's own repositories, you should also install the
280 ``debcargo-dbgsym`` package, otherwise the stack trace will be next to useless.
281 Make sure you have the `debug repository <https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols>`_
282 enabled in your APT sources.