(Backtrace): Document that free-standing environments do not need

to have a `main' function.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index f30d5cd36aa9a5f200d18c93e0de18ac349a6c6a..93393b691985b6cc0d98a69503b881991ec802d2 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -11,6 +11,8 @@
        --with-sysroot.
        (Machine Code): Document possible problems with locations in
        shared libraries.
+       (Backtrace): Document that free-standing environments do not need
+       to have a `main' function.
 
 2005-06-18  Nick Roberts  <nickrob@snap.net.nz>
 

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index b9c65992476ca21832c3d01769d24ae83f3538ba..0dd2f55e7d2ee2226b302b63945e10ac41d6cd80 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -4300,7 +4300,11 @@ you are interested in, or recompile without optimizations.
 @cindex startup code, and backtrace
 Most programs have a standard user entry point---a place where system
 libraries and startup code transition into user code.  For C this is
-@code{main}.  When @value{GDBN} finds the entry function in a backtrace
+@code{main}@footnote{
+Note that embedded programs (the so-called ``free-standing''
+environment) are not required to have a @code{main} function as the
+entry point.  They could even have multiple entry points.}.
+When @value{GDBN} finds the entry function in a backtrace
 it will terminate the backtrace, to avoid tracing into highly
 system-specific (and generally uninteresting) code.