diff options
| -rw-r--r-- | documentation/ref-manual/usingpoky.xml | 33 |
1 files changed, 23 insertions, 10 deletions
diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml index a7a63bd8cb..79322dd198 100644 --- a/documentation/ref-manual/usingpoky.xml +++ b/documentation/ref-manual/usingpoky.xml | |||
| @@ -166,19 +166,32 @@ | |||
| 166 | <section id='usingpoky-debugging-viewing-logs-from-failed-tasks'> | 166 | <section id='usingpoky-debugging-viewing-logs-from-failed-tasks'> |
| 167 | <title>Viewing Logs from Failed Tasks</title> | 167 | <title>Viewing Logs from Failed Tasks</title> |
| 168 | 168 | ||
| 169 | <para>The log file for shell tasks is available in | 169 | <para> |
| 170 | <filename>${WORKDIR}/temp/log.do_<replaceable>taskname</replaceable>.pid</filename>. | 170 | You can find the log for a task in the file |
| 171 | For example, the <filename>do_compile</filename> task for the QEMU minimal image for the x86 | 171 | <filename>${WORKDIR}/temp/log.do_</filename><replaceable>taskname</replaceable><filename>.</filename><replaceable>pid</replaceable>. |
| 172 | machine (<filename>qemux86</filename>) might be | 172 | For example, the log for the |
| 173 | <filename>tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_compile.20830</filename>. | 173 | <link linkend='ref-tasks-compile'><filename>do_compile</filename></link> |
| 174 | To see what | 174 | task of the QEMU minimal image for the x86 machine |
| 175 | <ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink> | 175 | (<filename>qemux86</filename>) might be in |
| 176 | runs to generate that log, look at the corresponding | 176 | <filename>tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_compile.</filename><replaceable>pid</replaceable>. |
| 177 | <filename>run.do_<replaceable>taskname</replaceable>.pid</filename> file located in the same directory. | 177 | To see the commands |
| 178 | <ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink> ran | ||
| 179 | to generate a log, look at the corresponding | ||
| 180 | <filename>run.do_</filename><replaceable>taskname</replaceable><filename>.</filename><replaceable>pid</replaceable> | ||
| 181 | file in the same directory. | ||
| 178 | </para> | 182 | </para> |
| 179 | 183 | ||
| 180 | <para> | 184 | <para> |
| 181 | Presently, the output from Python tasks is sent directly to the console. | 185 | <filename>log.do_</filename><replaceable>taskname</replaceable> and |
| 186 | <filename>run.do_</filename><replaceable>taskname</replaceable> | ||
| 187 | are actually symbolic links to | ||
| 188 | <filename>log.do_</filename><replaceable>taskname</replaceable><filename>.</filename><replaceable>pid</replaceable> | ||
| 189 | and | ||
| 190 | <filename>log.run_</filename><replaceable>taskname</replaceable><filename>.</filename><replaceable>pid</replaceable>, | ||
| 191 | where <replaceable>pid</replaceable> is the PID the task had when | ||
| 192 | it ran. | ||
| 193 | The symlinks always point to the files corresponding to the most | ||
| 194 | recent run. | ||
| 182 | </para> | 195 | </para> |
| 183 | </section> | 196 | </section> |
| 184 | 197 | ||
