wine.md: mention loading wine symbols and remove excess paragraph

Author: Hi-Angel

wine.md

@@ -1,7 +1,3 @@
 # Debugging
-
-It is possible to create a build of wine, and then to run wine right from the build directory. For example, `wine-git` from AUR creates two wine directories `build-32` and `build-64`. It is then possible to enter them, and use `make` command to rebuild; and use full path to `wine` symlink inside that build directory to run wine from there.
-
-# Misc
-
-* **running WINE from a bulid dir**: it will provide a `./wine → tools/winewrapper` symlink that is a shell-script wrapper setting up the necessary env. variables and running wine. If you really want, you may do that manually with a `LD_LIBRARY_PATH=libs/wine WINELOADER=loader/wine loader/wine /tmp/my.exe`
+* **running WINE from a build dir**: it will provide a `./wine → tools/winewrapper` symlink that is a shell-script wrapper setting up the necessary env. variables and running wine. If you really want, you may do that manually with a `LD_LIBRARY_PATH=libs/wine WINELOADER=loader/wine loader/wine /tmp/my.exe`
+* **loading WINE's debugging symbols**: note, this is not about `winedbg --gdb`, this is about running in `gdb` wine itself. `source` [this script](https://github.com/rbernon/wine/blob/develop/tools/gdbinit.py), and then, once you stopped at breakpoint, execute a `load-symbol-files`/`lsf`. As of writing the words, this command needs to be executed every time a module gets loaded, it won't do that automatically.