Update information about debuginfo configuration

src/compiler-debugging.md

@@ -47,7 +47,7 @@ stack backtrace:
 ```
 
 If you want line numbers for the stack trace, you can enable
-`debuginfo-lines=true` or `debuginfo=true` in your config.toml and rebuild the
+`debuginfo-level = 1` or `debuginfo-level = 2` in your config.toml and rebuild the
 compiler. Then the backtrace will look like this:
 
 ```text

src/how-to-build-and-run.md

@@ -36,11 +36,9 @@ debug-assertions = true
 # performance perhaps (less inlining) but it's worth it.
 codegen-units = 0
 
-# I always enable full debuginfo, though debuginfo-lines is more important.
-debuginfo = true
-
-# Gives you line numbers for backtraces.
-debuginfo-lines = true
+# I always enable full debuginfo, however the line debuginfo (which is a more important part
+# and enables e.g. line numbers in backtraces) is enabled by `debuginfo-level = 1` too.
+debuginfo-level = 2
 ```
 
 ### What is `x.py`?

src/profiling/with_perf.md

@@ -7,8 +7,8 @@ This is a guide for how to profile rustc with [perf](https://perf.wiki.kernel.or
 - Get a clean checkout of rust-lang/master, or whatever it is you want
   to profile.
 - Set the following settings in your `config.toml`:
-  - `debuginfo-lines = true`
-  - `use-jemalloc = false` — lets you do memory use profiling with valgrind 
+  - `debuginfo-level = 1` - enables line debuginfo
+  - `use-jemalloc = false` - lets you do memory use profiling with valgrind
   - leave everything else the defaults
 - Run `./x.py build` to get a full build
 - Make a rustup toolchain pointing to that result