OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

* gdbint.texinfo (Symbol Handling): Add a section 

on memory management.
This commit is contained in:
Daniel Jacobowitz 2006-02-06 22:14:31 +00:00
parent 75eb734c5c
commit c91d38aa70
2 changed files with 23 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2006-02-06 Daniel Jacobowitz <dan@codesourcery.com>
* gdbint.texinfo (Symbol Handling): Add a section
on memory management.
2006-02-06 Vladimir Prus <ghost@cs.msu.su>
* gdb.texinfo (Breakpoint table commands): Document the fullname

20
gdb/doc/gdbint.texinfo
View File

@ -9,7 +9,7 @@
@ifinfo
This file documents the internals of the GNU debugger @value{GDBN}.
Copyright (C) 1990, 1991, 1992, 1993, 1994, 1996, 1998, 1999, 2000, 2001,
2002, 2003, 2004, 2005
2002, 2003, 2004, 2005, 2006
Free Software Foundation, Inc.
Contributed by Cygnus Solutions. Written by John Gilmore.
Second Edition by Stan Shebs.
@ -49,7 +49,7 @@ Free Documentation License''.
@vskip 0pt plus 1filll
Copyright @copyright{} 1990,1991,1992,1993,1994,1996,1998,1999,2000,2001,
2002, 2003, 2004, 2005 Free Software Foundation, Inc.
2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1 or
@ -1985,6 +1985,22 @@ will only ever be implemented by one object file format may be called
directly. This interface should be described in a file
@file{bfd/lib@var{xyz}.h}, which is included by @value{GDBN}.
@section Memory Management for Symbol Files
Most memory associated with a loaded symbol file is stored on
its @code{objfile_obstack}. This includes symbols, types,
namespace data, and other information produced by the symbol readers.
Because this data lives on the objfile's obstack, it is automatically
released when the objfile is unloaded or reloaded. Therefore one
objfile must not reference symbol or type data from another objfile;
they could be unloaded at different times.
User convenience variables, et cetera, have associated types. Normally
these types live in the associated objfile. However, when the objfile
is unloaded, those types are deep copied to global memory, so that
the values of the user variables and history items are not lost.
@node Language Support