You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/faq/index.html
+6-4Lines changed: 6 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -118,7 +118,7 @@ <h2 id="how-to-single-step-empty-loops">How to single-step empty loops?</h2>
118
118
<p>I’m trying to single-step a simple loop, but execution does not stop after a single iteration, the target runs continuously, with permanent interactions with the debugger.</p>
119
119
</blockquote>
120
120
121
-
<p>The current GDB has a problem with placing breakpoints <strong>in simple loops</strong>, and <strong>single-stepping fails</strong>. The problem was already reported (<ahref="https://bugs.launchpad.net/gcc-arm-embedded/+bug/1401565">bug 1401565</a>). If you rally need this, switch to assembly view and single-stepping is again functional.</p>
121
+
<p>The current GDB has a problem with placing breakpoints <strong>in simple loops</strong>, and <strong>single-stepping fails</strong>. The problem was already reported (<ahref="https://bugs.launchpad.net/gcc-arm-embedded/+bug/1401565">bug 1401565</a>). If you really need this, switch to assembly view and single-stepping is again functional.</p>
122
122
123
123
<h2id="why-thedebugging-flow-with--og-is-sometimesjumpy">Why the debugging flow with -Og is sometimes jumpy?</h2>
124
124
@@ -128,13 +128,15 @@ <h2 id="why-thedebugging-flow-with--og-is-sometimesjumpy">Why the debugging flo
128
128
129
129
<p>In GCC prior 4.9, the definition of <strong>-Og</strong> needs a small adjustment, also add the <strong>-fno-move-loop-invariants</strong> option to the Debug configuration; this will prevent the compiler to move some constant parts of the loop outside it and the execution flow will be more easy to follow. The problem was already reported (<ahref="https://bugs.launchpad.net/gcc-arm-embedded/+bug/1395077">bug 1395077</a>). Starting with 4.9, the -fno-move-loop-invariants is added automatically to -Og.</p>
130
130
131
-
<h2id="how-can-i-add-new-tickets-if-no-create-ticket-button-is-available">How can I add new tickets if no Create Ticket button is available?</h2>
131
+
<h2id="how-can-i-add-new-sourceforge-tickets-if-no-create-ticket-button-is-available">How can I add new SourceForge tickets if no Create Ticket button is available?</h2>
132
132
133
133
<blockquote>
134
134
<p>Please excuse me for not using the support ticket tool you provided on sourceforge but I seem to be too incompetent to even spot some type of “add request” button.</p>
135
135
</blockquote>
136
136
137
-
<p>To be able to add new tickets to the SourceForge trackers, you need to log-in to SourceForge, and so the <strong>Create Ticket</strong> button will become visible.</p>
137
+
<p>Following the migration to GitHub, the SourceForge ticketing system was configured as read-only, and new tickets can no longer be added.</p>
138
+
139
+
<p>Please login to GitHub and use the GitHub Issues trackers.</p>
138
140
139
141
<h2id="plug-ins-update-from-05x-running-on-junoto-current-version-fails">Plug-ins update from 0.5.x running on Juno to current version fails</h2>
140
142
@@ -273,7 +275,7 @@ <h3 id="i-changed-the-remove-command-but-the-value-is-not-effective">I changed t
Copy file name to clipboardExpand all lines: toolchain/install/index.html
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,9 @@ <h2 id="overview">Overview</h2>
87
87
<li>the host/development platform is the platform where the development tools are executed, usually as cross compilers, and can be, in our case, any platform that supports Eclipse, for example Windows, OS X, GNU/Linux, BSD, etc.</li>
88
88
</ul>
89
89
90
-
<p>Be sure you select the proper toolchain for the target platform, otherwise builds will not succeed, or the generated applications will fail to run. <strong>Do not</strong> try to use the GCC ARM Embedded to build GNU/Linux applications, because the executables will not run on anything than bare metal, and <strong>do not try to use the Linaro toolchains for bare metal applications</strong>.</p>
90
+
<blockquote>
91
+
<p>Note: Be sure you select the proper toolchain for the target platform, otherwise builds will not succeed, or the generated applications will fail to run. <strong>Do not</strong> try to use the GCC ARM Embedded to build GNU/Linux applications, because the executables will not run on anything than bare metal, and <strong>do not try to use the Linaro toolchains for bare metal applications</strong>.</p>
92
+
</blockquote>
91
93
92
94
<p>The installation details described below assume the selection of the GCC ARM Embedded toolchain. For other toolchains, please follow the specific installation instructions.</p>
0 commit comments