From b7a24051cf6415d9482b7af73375ae5637b7cba1 Mon Sep 17 00:00:00 2001 From: Jim Kingdon Date: Thu, 2 Feb 1995 04:31:24 +0000 Subject: [PATCH] * stabs.texinfo (Source Files): Document N_SO used to mark the end of a source file. --- gdb/doc/ChangeLog | 5 +++++ gdb/doc/stabs.texinfo | 9 +++++++++ 2 files changed, 14 insertions(+) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 24d28fd12bb..e5aa67aa088 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +Wed Feb 1 20:26:36 1995 Jim Kingdon (kingdon@lioth.cygnus.com) + + * stabs.texinfo (Source Files): Document N_SO used to mark the end + of a source file. + Mon Jan 23 14:23:37 1995 Jim Kingdon (kingdon@lioth.cygnus.com) * gdb.texinfo (Processes): New node. diff --git a/gdb/doc/stabs.texinfo b/gdb/doc/stabs.texinfo index 24f7149a108..62e13a73c36 100644 --- a/gdb/doc/stabs.texinfo +++ b/gdb/doc/stabs.texinfo @@ -435,6 +435,15 @@ Instead of @code{N_SO} symbols, XCOFF uses a @code{.file} assembler directive which assembles to a standard COFF @code{.file} symbol; explaining this in detail is outside the scope of this document. +@c FIXME: Exactly when should the empty N_SO be used? Why? +If it is useful to indicate the end of a source file, this is done with +an @code{N_SO} symbol with an empty string for the name. The value is +the address of the end of the text section for the file. For some +systems, there is no indication of the end of a source file, and you +just need to figure it ended when you see an @code{N_SO} for a different +source file, or a symbol ending in @code{.o} (which at least some +linkers insert to mark the start of a new @code{.o} file). + @node Include Files @section Names of Include Files -- 2.30.2