diff -r 48780e181b38 -r 578be2adaf3e Symbian3/PDK/Source/GUID-1E43E258-A926-5D24-B0A5-8756491C687F.dita
--- a/Symbian3/PDK/Source/GUID-1E43E258-A926-5D24-B0A5-8756491C687F.dita	Tue Jul 20 12:00:49 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-1E43E258-A926-5D24-B0A5-8756491C687F.dita	Fri Aug 13 16:47:46 2010 +0100
@@ -173,7 +173,7 @@
 while <codeph>B()</codeph> is active. </p> <p>This scenario happens frequently
 when <codeph>B()</codeph> allocates a buffer (e.g. <xref href="GUID-0B9C8884-6BFF-35E2-AA6F-E4057B85AFCF.dita"><apiname>TBuf</apiname></xref>)
 on the stack which overlaps old stack frames. </p> <fig id="GUID-FED8CC0F-F1A0-59C9-B082-2D3B499D00D5">
-<image href="GUID-A328F9E3-7D91-594A-A589-E8CE5FA9227A_d0e302145_href.png" placement="inline"/>
+<image href="GUID-A328F9E3-7D91-594A-A589-E8CE5FA9227A_d0e299982_href.png" placement="inline"/>
 </fig> </li>
 </ul> <p>If you want to trace applications loaded into RAM, then stack tracing
 is more difficult because RAM-loaded DLLs are given addresses assigned at
@@ -340,7 +340,7 @@
 </codeblock> <p>noting that: <codeph>SP = R13</codeph>, <codeph>FP = R11</codeph>, <codeph>IP
 =           R12</codeph>, <codeph>LR = R14</codeph>, and <codeph>PC = R15</codeph>. </p> <p>This
 code creates the following stack frame: </p> <fig id="GUID-5CE044A2-CDD0-5A09-B824-BAF46324AB27">
-<image href="GUID-F12437C5-BD96-5B43-AD76-614CFAB104D2_d0e302343_href.png" placement="inline"/>
+<image href="GUID-F12437C5-BD96-5B43-AD76-614CFAB104D2_d0e300180_href.png" placement="inline"/>
 </fig> <p>Looking at the example session listed in when <xref href="GUID-1E43E258-A926-5D24-B0A5-8756491C687F.dita#GUID-1E43E258-A926-5D24-B0A5-8756491C687F/GUID-877742A5-F07F-54B6-B871-255FAAE790EB">tracing through the stack heuristically</xref>. in which the crash is due
 to a panic, the FP value is the R11 value; this is <codeph>0x6571de70</codeph>.
 This gives us the innermost stack frame: </p> <codeblock id="GUID-DE5FFB23-A85D-562F-858B-CFF407448E36" xml:space="preserve">6571de64:    e8 de 71 65 &lt;------------- pointer to previous stack frame 
@@ -378,7 +378,7 @@
 sub        sp, #28
 add        r7, sp, #12 /* R7 is THUMB frame pointer */
 </codeblock> <p>and this creates the following stack frame: </p> <fig id="GUID-85FAEE94-6D61-5D6B-84CB-6A9491927077">
-<image href="GUID-5CF162CA-4395-58AC-A318-2BF178276A57_d0e302420_href.png" placement="inline"/>
+<image href="GUID-5CF162CA-4395-58AC-A318-2BF178276A57_d0e300257_href.png" placement="inline"/>
 </fig> <p>A call stack can mix ARM and THUMB frames. Odd return addresses
 are used for THUMB code and even ones for ARM code. </p> </section>
 </conbody></concept>
\ No newline at end of file