summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html
diff options
context:
space:
mode:
authorTimo Mueller <timo.mueller@bmw-carit.de>2013-02-08 09:16:33 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-02-14 17:25:35 +0000
commita41a805500cab281fba15bd8e5d3e60b88d0d4be (patch)
tree9973678912b57cfdef5b1f9676794a556b4d8966 /documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html
parent768152340898cbb9faed6e8865a4e35c69833230 (diff)
downloadpoky-a41a805500cab281fba15bd8e5d3e60b88d0d4be.tar.gz
documentation: Part 1 of 2 updates to integrating docs to Eclipse help.
Hi, the generation of eclipse help files has been merged from the timo branch to the master. Since the creation of the timo branch there have been some changes to the master branch (e.g. new documentation, renamed documentation). This patch set does some cleanup for the renamed documentation and adds eclipse help generation support to the new documentation. 01: Removes the 'the' from the document titles 02..04: Cleanup obsolete artifacts resulting from the merge 05..08: Add eclipse help generation for ref-manual 09..13: Add eclipse help generation for kernel-dev 14..18: Add eclipse help generation for profile-manual Best regards, Timo This patch set originally contained 18 patches. I (Scott Rifenbark) had to push these changes as two parts. This is the first part. It does not include creation of the three cusomization files. (From yocto-docs rev: 9b1889f6e31ee70dae704fa08763fb9196616dad) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html')
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html43
1 files changed, 0 insertions, 43 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html
deleted file mode 100644
index 80a19f98a4..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/debugging.html
+++ /dev/null
@@ -1,43 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>3.2.4.1. Debugging</title>
5<link rel="stylesheet" type="text/css" href="../book.css">
6<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
7<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
8<link rel="up" href="tips-and-tricks.html" title="3.2.4. Tips and Tricks">
9<link rel="prev" href="tips-and-tricks.html" title="3.2.4. Tips and Tricks">
10<link rel="next" href="invalidating-shared-state.html" title="3.2.4.2. Invalidating Shared State">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.2.4.1. Debugging">
13<div class="titlepage"><div><div><h4 class="title">
14<a name="debugging"></a>3.2.4.1. Debugging</h4></div></div></div>
15<p>
16 When things go wrong, debugging needs to be straightforward.
17 Because of this, the Yocto Project team included strong debugging
18 tools:
19 </p>
20<div class="itemizedlist"><ul class="itemizedlist" type="disc">
21<li class="listitem"><p>Whenever a shared state package is written out, so is a
22 corresponding <code class="filename">.siginfo</code> file.
23 This practice results in a pickled python database of all
24 the metadata that went into creating the hash for a given shared state
25 package.</p></li>
26<li class="listitem"><p>If BitBake is run with the <code class="filename">--dump-signatures</code>
27 (or <code class="filename">-S</code>) option, BitBake dumps out
28 <code class="filename">.siginfo</code> files in
29 the stamp directory for every task it would have executed instead of
30 building the specified target package.</p></li>
31<li class="listitem"><p>There is a <code class="filename">bitbake-diffsigs</code> command that
32 can process these <code class="filename">.siginfo</code> files.
33 If one file is specified, it will dump out the dependency
34 information in the file.
35 If two files are specified, it will compare the two files and dump out
36 the differences between the two.
37 This allows the question of "What changed between X and Y?" to be
38 answered easily.</p></li>
39</ul></div>
40<p>
41 </p>
42</div></body>
43</html>