--print-cmd-oneline: document its existence in the usual locations

This commit is contained in:
Ciro Santilli 六四事件 法轮功
2020-05-07 06:00:05 +00:00
parent 5d41b3ba67
commit 12ed05f893

View File

@@ -567,6 +567,8 @@ So observe that the command contains:
* `+`: sign to differentiate it from program stdout, much like bash `-x` output. This is not a valid part of the generated Bash command however. * `+`: sign to differentiate it from program stdout, much like bash `-x` output. This is not a valid part of the generated Bash command however.
* the actual command nicely, indented and with arguments broken one per line, but with continuing backslashes so you can just copy paste into a terminal * the actual command nicely, indented and with arguments broken one per line, but with continuing backslashes so you can just copy paste into a terminal
+
For setups that don't support the newline e.g. <<gem5-eclipse-configuration,Eclipse debugging>>, you can turn them off with `--print-cmd-oneline`
* `;`: both a valid part of the Bash command, and a visual mark the end of the command * `;`: both a valid part of the Bash command, and a visual mark the end of the command
For the specific case of running emulators such as QEMU, the last command is also automatically placed in a file for your convenience and later inspection: For the specific case of running emulators such as QEMU, the last command is also automatically placed in a file for your convenience and later inspection:
@@ -13244,7 +13246,13 @@ I recommend the following settings, tested in Eclipse 2019.09, Ubuntu 18.04:
*** ./src/ in the source tree *** ./src/ in the source tree
*** the ISA specific build directory which contains some self-generated stuff, e.g.: out/gem5/default/build/ARM *** the ISA specific build directory which contains some self-generated stuff, e.g.: out/gem5/default/build/ARM
To run and GDB step debug the executable, just copy the full command line from the output `./run`, and configure it into Eclipse. To run and GDB step debug the executable, just copy the <<dry-run,full command line without newlines>> from your run command (Eclipse does not like newlines for the arguments), e.g.:
....
./run --emulator gem5 --print-cmd-oneline
....
and configure it into Eclipse as usual.
==== gem5 Python C++ interaction ==== gem5 Python C++ interaction