Lines Matching refs:we

26 Please also have a look at our list of [code quality tools](CODE_QUALITY.md) we
34 possible, however. In order to simplify testing for cases like this we provide
177 right in your editor of choice (with the right plugin installed). When using mkosi, we can run clan…
204 To be able to navigate to include files of systemd's dependencies, we need to make the /usr/include…
219 image, edit the 20-local.conf file we created earlier and add the following contents under the `[Pa…
230 Because mkosi needs to run as root, we also need to make sure we can enter the root password when t…
232 scripts, we use an askpass provider. This is a program that sudo will launch if it detects it's bei…
256 To simplify debugging systemd when testing changes using mkosi, we're going to show how to attach
260 To allow VSCode's debugger to attach to systemd running in a mkosi image, we have to make sure it c…
274 Now we need to configure VSCode. First, make sure the C/C++ extension is installed. If you're alrea…
285 With the extension set up, we can create the launch.json file in the .vscode/ directory to tell the…
324 Now that the debugger knows how to connect to our process in the container/VM and we've set up the …
350 If the debugger is too slow to attach to examine an early boot code passage, we can uncomment the
351 call to `debug_break()` inside of `efi_main()`. As soon as the debugger has control we can then run
355 To debug systemd-boot in an IDE such as VSCode we can use a launch configuration like this: