diff options
| author | Alexander Kanavin <alex.kanavin@gmail.com> | 2024-03-18 16:02:09 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2024-03-19 15:22:27 +0000 |
| commit | 27e72a5f13ab8c9d09f9e88a95bf3316a937045f (patch) | |
| tree | c4fce1bebff47475a73448d3a233e8e24674f44b /documentation/dev-manual/debugging.rst | |
| parent | bc06390947e560bbd999fc09b789cee93a324c7d (diff) | |
| download | poky-27e72a5f13ab8c9d09f9e88a95bf3316a937045f.tar.gz | |
dev-manual: improve descriptions of 'bitbake -S printdiff'
Try to particularly emphasize that it can be used to find
out why something rebuilds when it shouldn't.
(From yocto-docs rev: cfaf2707b4a77888316d5eb24bf41ccc21e2c12b)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/debugging.rst')
| -rw-r--r-- | documentation/dev-manual/debugging.rst | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/documentation/dev-manual/debugging.rst b/documentation/dev-manual/debugging.rst index ce29815e9f..e20637e1c6 100644 --- a/documentation/dev-manual/debugging.rst +++ b/documentation/dev-manual/debugging.rst | |||
| @@ -339,7 +339,10 @@ BitBake has determined by doing the following: | |||
| 339 | :term:`BB_BASEHASH_IGNORE_VARS` | 339 | :term:`BB_BASEHASH_IGNORE_VARS` |
| 340 | information. | 340 | information. |
| 341 | 341 | ||
| 342 | There is also a ``bitbake-diffsigs`` command for comparing two | 342 | Debugging signature construction and unexpected task executions |
| 343 | =============================================================== | ||
| 344 | |||
| 345 | There is a ``bitbake-diffsigs`` command for comparing two | ||
| 343 | ``siginfo`` or ``sigdata`` files. This command can be helpful when | 346 | ``siginfo`` or ``sigdata`` files. This command can be helpful when |
| 344 | trying to figure out what changed between two versions of a task. If you | 347 | trying to figure out what changed between two versions of a task. If you |
| 345 | call ``bitbake-diffsigs`` with just one file, the command behaves like | 348 | call ``bitbake-diffsigs`` with just one file, the command behaves like |
| @@ -356,8 +359,12 @@ BitBake command-line options:: | |||
| 356 | .. note:: | 359 | .. note:: |
| 357 | 360 | ||
| 358 | Two common values for `SIGNATURE_HANDLER` are "none" and "printdiff", which | 361 | Two common values for `SIGNATURE_HANDLER` are "none" and "printdiff", which |
| 359 | dump only the signature or compare the dumped signature with the cached one, | 362 | dump only the signature or compare the dumped signature with the most recent one, |
| 360 | respectively. | 363 | respectively. "printdiff" will try to establish the most recent |
| 364 | signature match (e.g. in the sstate cache) and then | ||
| 365 | compare the matched signatures to determine the stamps and delta | ||
| 366 | where these two stamp trees diverge. This can be used to determine why | ||
| 367 | tasks need to be re-run in situations where that is not expected. | ||
| 361 | 368 | ||
| 362 | Using BitBake with either of these options causes BitBake to dump out | 369 | Using BitBake with either of these options causes BitBake to dump out |
| 363 | ``sigdata`` files in the ``stamps`` directory for every task it would | 370 | ``sigdata`` files in the ``stamps`` directory for every task it would |
