/usr/share/help/ro/anjuta-manual/debug-tips.page is in anjuta-common 2:3.10.2-0ubuntu2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 | <?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" type="topic" style="task" id="debug-tips" xml:lang="ro">
<info xmlns:facet="http://projectmallard.org/facet/1.0/">
<facet:tag key="all-pages" value="whatever"/> <!--Include page in index-->
<link type="guide" xref="index#anjuta-debug" group="fifth"/>
<revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
<desc>
Debugging tips and tricks.
</desc>
<credit type="author">
<name>Sébastien Granjoux</name>
<email>seb.sfo@free.fr</email>
</credit>
<credit type="editor">
<name>Philip Chimento</name>
<email>philip.chimento@gmail.com</email>
</credit>
</info>
<title>Indicații pentru depanare</title>
<section>
<title>Fixing GLib/GTK+ critical errors</title>
<p>Sometimes it can be difficult to track down where GLib critical errors are
occurring, since they do not stop the program.
You can set the program to stop as soon as it gets a GLib critical error, by setting
the environment variable <sys>G_DEBUG</sys> to the value
<sys>fatal_criticals</sys>.</p>
<steps>
<item>
<p>Open the <link xref="run-parameters-dialog"/> by selecting
<guiseq><gui>Run</gui><gui>Program Parameters...</gui></guiseq> from the
main menu.</p>
</item>
<item>
<p>Click the plus sign next to <gui>Environment Variables</gui> to expand
the list of environment variables.</p>
</item>
<item>
<p>Click <gui>New</gui> to add a new entry to the list.</p>
</item>
<item>
<p>Fill in <gui>Name</gui> with <input>G_DEBUG</input> and <gui>Value</gui>
with <input>fatal_criticals</input>.</p>
</item>
<item>
<p>Click <gui>Apply</gui> to confirm the changes.</p>
</item>
<item>
<p>Run the program with the debugger by selecting
<guiseq><gui>Run</gui><gui>Debug Program</gui></guiseq> from the main menu.</p>
</item>
<item>
<p>Use the program until the critical error occurs.</p>
</item>
<item>
<p>When the debugger stops your program, look at the
<link xref="debug-stack"/> to check where this error comes from.</p>
</item>
</steps>
<p>The top function with frame number 0 is in GLib, so you have to look
down in the stack. Typically the error originates from the topmost
function that belongs to your program.</p>
</section>
</page>
|