From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Stephane Carrez <Stephane.Carrez@worldnet.fr>,
gdb-patches@sourceware.cygnus.com, Jim Blandy <jimb@cygnus.com>
Subject: Re: path for gdb/dwarf2read.c, support 16-bit targets in dwarf-2
Date: Tue, 28 Mar 2000 08:24:00 -0000 [thread overview]
Message-ID: <npln332hbu.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <38C225F3.9E236A55@cygnus.com>
> > elf16 is not a good idea. I think we must not mix the size of cpu
> > address with the format of ELF files. The ELF file can be larger than
> > 64K and we might need indexes larger than 16-bit.
>
> When I say ``elf16'', I was thinking of an elf object file that has 16
> bit addresses. I'm not sure what other consequences such a move would
> have.
>
> Is there any reason why s->arch_size isn't 16 in your case?
s->arch_size is not an especially meaningful field. It exists only to
indicate whether you've got an ELF32 or ELF64 format file.
I think inventing a new ELF16 file format is a bad idea. There are a
zillion things to take into account. It's much simpler to just use
ELF32, and only link things into the lower 64k, which is what
we've done with other 16-bit processors in the past.
If you want to know the actual processor address size, there's a
different BFD field whose job is to provide that information. That's
bfd_arch_bits_per_address, which Stephane suggested we use instead.
In general, the change that has dwarf2read checking the ELF backend
data has just been a pain from day one. I remember fixing related
dependency problems, people on the binutils list saying "This looks
really wrong," and so on. GDB shouldn't be using internal BFD
headers, and consulting internal ELF BFD data structures.
I also buy Jim Kingdon's argument that it shouldn't be necessary to
mask off the upper bits. The data in the ELF file should be correct.
I'm going to revert the change which introduced
address_significant_size in the first place. If this causes problems,
then we'll fix the bug correctly.
From jimb@zwingli.cygnus.com Tue Mar 28 08:24:00 2000
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: gdb-patches@sourceware.cygnus.com
Subject: [PATCH] Don't trim addresses in Dwarf debug info
Date: Tue, 28 Mar 2000 08:24:00 -0000
Message-id: <200003281624.LAA23161@zwingli.cygnus.com>
X-SW-Source: 2000-03/msg00645.html
Content-length: 4499
I've committed this:
2000-03-27 Jim Blandy <jimb@redhat.com>
* dwarf2read.c: Revert Andrew Cagney's change of Dec 15, 1997.
Don't include "bfd-elf.h".
(address_significant_size): Delete variable.
(dwarf2_build_psymtabs_hard): Don't set it, or check for
consistency between it and the Dwarf 2 compilation unit header
address size.
(read_address): Don't mask off bits above
address_significant_size.
* Makefile.in (dwarf2read.o): Don't depend on $(elf_bfd_h).
(elf_bfd_h): Remove variable; it's no longer used.
Index: gdb/dwarf2read.c
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/dwarf2read.c,v
retrieving revision 2.37
diff -c -r2.37 dwarf2read.c
*** gdb/dwarf2read.c 2000/02/29 07:14:21 2.37
--- gdb/dwarf2read.c 2000/03/27 20:50:09
***************
*** 27,33 ****
#include "defs.h"
#include "bfd.h"
- #include "elf-bfd.h"
#include "symtab.h"
#include "gdbtypes.h"
#include "symfile.h"
--- 27,32 ----
***************
*** 546,560 ****
whatever scope is currently getting read. */
static int address_size;
- /* Some elf32 object file formats while linked for a 32 bit address
- space contain debug information that has assumed 64 bit
- addresses. Eg 64 bit MIPS target produced by GCC/GAS/LD where the
- symbol table contains 32bit address values while its .debug_info
- section contains 64 bit address values.
- ADDRESS_SIGNIFICANT_SIZE specifies the number significant bits in
- the ADDRESS_SIZE bytes read from the file */
- static int address_significant_size;
-
/* Externals references. */
extern int info_verbose; /* From main.c; nonzero => verbose */
--- 545,550 ----
***************
*** 937,945 ****
int comp_unit_has_pc_info;
CORE_ADDR lowpc, highpc;
- /* Number of bytes of any addresses that are signficant */
- address_significant_size = get_elf_backend_data (abfd)->s->arch_size / 8;
-
info_ptr = dwarf_info_buffer;
abbrev_ptr = dwarf_abbrev_buffer;
--- 927,932 ----
***************
*** 980,992 ****
(long) (beg_of_comp_unit - dwarf_info_buffer));
return;
}
- if (address_size < address_significant_size)
- {
- error ("Dwarf Error: bad address size (%ld) in compilation unit header (offset 0x%lx + 11).",
- (long) cu_header.addr_size,
- (long) (beg_of_comp_unit - dwarf_info_buffer));
- }
-
/* Read the abbrevs for this compilation unit into a table */
dwarf2_read_abbrevs (abfd, cu_header.abbrev_offset);
make_cleanup (dwarf2_empty_abbrev_table, NULL);
--- 967,972 ----
***************
*** 3499,3516 ****
default:
/* *THE* alternative is 8, right? */
abort ();
- }
- /* If the address being read is larger than the address that is
- applicable for the object file format then mask it down to the
- correct size. Take care to avoid unnecessary shift or shift
- overflow */
- if (address_size > address_significant_size
- && address_significant_size < sizeof (CORE_ADDR))
- {
- CORE_ADDR mask = ((CORE_ADDR) 0) - 1;
- retval &= ~(mask << (address_significant_size * 8));
}
! return retval;
}
static char *
--- 3479,3487 ----
default:
/* *THE* alternative is 8, right? */
abort ();
}
!
! return retval;
}
static char *
Index: gdb/Makefile.in
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/Makefile.in,v
retrieving revision 1.760
diff -c -r1.760 Makefile.in
*** gdb/Makefile.in 2000/03/20 04:36:02 1.760
--- gdb/Makefile.in 2000/03/27 20:50:10
***************
*** 507,513 ****
getopt_h = $(INCLUDE_DIR)/getopt.h
floatformat_h = $(INCLUDE_DIR)/floatformat.h
bfd_h = $(BFD_DIR)/bfd.h
- elf_bfd_h = $(BFD_SRC)/elf-bfd.h
dis-asm_h = $(INCLUDE_DIR)/dis-asm.h
remote-sim_h = $(INCLUDE_DIR)/remote-sim.h
--- 507,512 ----
***************
*** 1251,1257 ****
$(expression_h) $(gdbtypes_h) language.h objfiles.h symfile.h \
$(symtab_h) gdb_string.h
! dwarf2read.o: dwarf2read.c $(bfd_h) $(elf_bfd_h) buildsym.h $(defs_h) \
$(expression_h) $(gdbtypes_h) language.h objfiles.h symfile.h \
$(symtab_h) gdb_string.h
--- 1250,1256 ----
$(expression_h) $(gdbtypes_h) language.h objfiles.h symfile.h \
$(symtab_h) gdb_string.h
! dwarf2read.o: dwarf2read.c $(bfd_h) buildsym.h $(defs_h) \
$(expression_h) $(gdbtypes_h) language.h objfiles.h symfile.h \
$(symtab_h) gdb_string.h
From jimb@zwingli.cygnus.com Tue Mar 28 08:26:00 2000
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim Kingdon <kingdon@redhat.com>, Stephane Carrez <Stephane.Carrez@worldnet.fr>, gdb-patches@sourceware.cygnus.com, Jim Blandy <jimb@cygnus.com>
Subject: Re: path for gdb/dwarf2read.c, support 16-bit targets in dwarf-2
Date: Tue, 28 Mar 2000 08:26:00 -0000
Message-id: <npk8in2h8y.fsf@zwingli.cygnus.com>
References: <38B2F3D3.54CF0AF0@worldnet.fr> <38BB5463.D6E5B75C@cygnus.com> <38C0D9D9.70987863@worldnet.fr> <38C225F3.9E236A55@cygnus.com> <bput8j8vi.fsf@rtl.cygnus.com> <38C737EE.513259B9@cygnus.com>
X-SW-Source: 2000-03/msg00646.html
Content-length: 1204
> > The whole address_significant_size code in dwarf2read.c strikes me as
> > a rather ugly kludge to work around bugs elsewhere in the tool chain.
> > If someone is supplying a 32 bit pointer to GDB on a 16 bit target,
> > shouldn't the rest of the tool chain be responsible for making sure
> > the high bits are zero rather than expecting GDB to mask it off?
> > Granted there might be complications here, like there are cases on
> > MIPS where we treat an address as signed rather than unsigned, but I'm
> > also pretty clear on whether that is actually design or just a bug. I
> > could be wrong/persuadable, of course, and perhaps someone has a
> > better idea of all this (in which case I'd suggest commenting
> > arch_size at bfd/elf-bfd.h and/or expanding comments at
> > bfd_arch_bits_per_address in bfd/archures.c).
>
> FYI, in the MIPS case it is a feature of the hardware. GDB has little
> choice in the matter.
Can you explain why, in the MIPS case, GCC/GAS/LD are unable to place
correct information in the upper bits of the Dwarf addresses?
(That sounds like a rhetorical question, but it's not. I'm having a
hard time imagining why address_significant_bits was the right
solution.)
From jimb@zwingli.cygnus.com Tue Mar 28 08:50:00 2000
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA] Avoid core dumping on corrupt stabs entry
Date: Tue, 28 Mar 2000 08:50:00 -0000
Message-id: <npity72g5n.fsf@zwingli.cygnus.com>
References: <20000327204057.A24783@cygnus.com>
X-SW-Source: 2000-03/msg00647.html
Content-length: 860
Approved, thanks.
> Any objections to this patch? It seems to be in the spirit of the rest
> of the file.
>
> cgf
>
> 2000-03-27 Christopher Faylor <cgf@cygnus.com>
>
> * partial-stab.h: Add one more check against corrupted or irregular
> stabs entry.
>
> Index: partial-stab.h
> ===================================================================
> RCS file: /cvs/cvsfiles/devo/gdb/partial-stab.h,v
> retrieving revision 2.68
> diff -u -p -r2.68 partial-stab.h
> --- partial-stab.h 1999/09/14 22:50:39 2.68
> +++ partial-stab.h 2000/03/28 01:37:53
> @@ -393,7 +393,7 @@ switch (CUR_SYMBOL_TYPE)
>
> #ifdef DBXREAD_ONLY
> /* See if this is an end of function stab. */
> - if (CUR_SYMBOL_TYPE == N_FUN && *namestring == '\000')
> + if (pst && CUR_SYMBOL_TYPE == N_FUN && *namestring == '\000')
> {
> unsigned long valu;
>
>
From shebs@shebs.cnchost.com Tue Mar 28 08:59:00 2000
From: Stan Shebs <shebs@shebs.cnchost.com>
To: gdb-patches@sourceware.cygnus.com
Cc: 3diff@gnu.org
Subject: GDB manual changes
Date: Tue, 28 Mar 2000 08:59:00 -0000
Message-id: <38E0E672.478B088F@shebs.cnchost.com>
X-SW-Source: 2000-03/msg00648.html
Content-length: 136933
I've just committed a pile of changes to the manual. This includes
the duplication of the top-level menu for the benefit of @ifhtml,
the re-removal of node links, and various formatting changes to
make @smallbook come out right (as requested by Brian Youmans).
I tested on 3.12, 3.12h (RH 6.1 version), and 4.0. Apparently
texi2html has a problem with the top-level menu that is under
@ifhtml, and it gets garbled, although 4.0 makeinfo -html works
fine (but it can only make one monster html file, sigh). It's
functionally no worse than before, but looks bad.
I'm still planning to rewrite the introduction to use a more
meaningful example program, and we still have undocumented
commands that ought to be mentioned, so this isn't the end,
but this should be a good base for the next round of tweaks.
(I left the remote protocol section mostly untouched, since JT
has a patch to apply.)
Stan
2000-03-28 Stan Shebs <shebs@apple.com>
* gdb.texinfo: Update dates, bump to Eighth Edition (note
expectation of additional changes before release), update
ISBN, add copy of top-level menu for @ifhtml, remove explicit
node links, rephrase and/or shorten lines to fix formatting
problem in both regular and @smallbook formats.
* annotate.texi: Shorten lines in example, use smallexample
consistently everywhere.
* Makefile.in: Add comment about texinfo 4.0 html generation.
(SFILES_INCLUDED): Add annotate.texi.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/doc/Makefile.in,v
retrieving revision 1.3
diff -p -r1.3 Makefile.in
*** Makefile.in 2000/03/24 07:27:24 1.3
--- Makefile.in 2000/03/28 16:33:45
*************** TEXIDIR=${gdbdir}/../texinfo
*** 40,45 ****
--- 40,49 ----
# where to find makeinfo, preferably one designed for texinfo-2
MAKEINFO=makeinfo
+ # Note that texinfo 4.0's makeinfo --html can only generate a
+ # single file, which would be too large, so continue to use
+ # texi2html. -sts 2000-03-28
+
MAKEHTML = texi2html
MAKEHTMLFLAGS = -glossary -menu -split_chapter
*************** TEXINDEX = texindex
*** 83,89 ****
DVIPS = dvips
# Main GDB manual's source files
! SFILES_INCLUDED = gdb-cfg.texi
SFILES_LOCAL = $(srcdir)/gdb.texinfo GDBvn.texi $(SFILES_INCLUDED)
--- 87,93 ----
DVIPS = dvips
# Main GDB manual's source files
! SFILES_INCLUDED = gdb-cfg.texi $(srcdir)/annotate.texi
SFILES_LOCAL = $(srcdir)/gdb.texinfo GDBvn.texi $(SFILES_INCLUDED)
Index: annotate.texi
===================================================================
RCS file: /cvs/src/src/gdb/doc/annotate.texi,v
retrieving revision 1.3
diff -p -r1.3 annotate.texi
*** annotate.texi 2000/03/24 07:30:06 1.3
--- annotate.texi 2000/03/28 16:33:45
***************
*** 60,68 ****
@chapter @value{GDBN} Annotations
@end ifclear
! This chapter describes annotations in @value{GDBN}, the GNU symbolic debugger.
! Annotations are designed to interface @value{GDBN} to graphical user interfaces
! or other similar programs which want to interact with @value{GDBN} at a
relatively high level.
@ignore
--- 60,68 ----
@chapter @value{GDBN} Annotations
@end ifclear
! This chapter describes annotations in @value{GDBN}. Annotations are
! designed to interface @value{GDBN} to graphical user interfaces or other
! similar programs which want to interact with @value{GDBN} at a
relatively high level.
@ignore
*************** additional information, and a newline.
*** 100,109 ****
cannot contain newline characters.
Any output not beginning with a newline and two @samp{control-z}
! characters denotes literal output from @value{GDBN}. Currently there is no need
! for @value{GDBN} to output a newline followed by two @samp{control-z} characters,
! but if there was such a need, the annotations could be extended with an
! @samp{escape} annotation which means those three characters as output.
A simple example of starting up @value{GDBN} with annotations is:
--- 100,110 ----
cannot contain newline characters.
Any output not beginning with a newline and two @samp{control-z}
! characters denotes literal output from @value{GDBN}. Currently there is
! no need for @value{GDBN} to output a newline followed by two
! @samp{control-z} characters, but if there was such a need, the
! annotations could be extended with an @samp{escape} annotation which
! means those three characters as output.
A simple example of starting up @value{GDBN} with annotations is:
*************** A simple example of starting up @value{G
*** 111,120 ****
$ gdb --annotate=2
GNU GDB 5.0
Copyright 2000 Free Software Foundation, Inc.
! GDB is free software, covered by the GNU General Public License, and you are
! welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
! There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "sparc-sun-sunos4.1.3"
^Z^Zpre-prompt
--- 112,123 ----
$ gdb --annotate=2
GNU GDB 5.0
Copyright 2000 Free Software Foundation, Inc.
! GDB is free software, covered by the GNU General Public License,
! and you are welcome to change it and/or distribute copies of it
! under certain conditions.
Type "show copying" to see the conditions.
! There is absolutely no warranty for GDB. Type "show warranty"
! for details.
This GDB was configured as "sparc-sun-sunos4.1.3"
^Z^Zpre-prompt
*************** quit
*** 126,144 ****
$
@end smallexample
! Here @samp{quit} is input to @value{GDBN}; the rest is output from @value{GDBN}. The three
! lines beginning @samp{^Z^Z} (where @samp{^Z} denotes a @samp{control-z}
! character) are annotations; the rest is output from @value{GDBN}.
@node Server Prefix
@section The Server Prefix
@cindex server prefix for annotations
! To issue a command to @value{GDBN} without affecting certain aspects of the state
! which is seen by users, prefix it with @samp{server }. This means that
! this command will not affect the command history, nor will it affect
! @value{GDBN}'s notion of which command to repeat if @key{RET} is pressed on a
! line by itself.
The server prefix does not affect the recording of values into the value
history; to print a value without recording it into the value history,
--- 129,148 ----
$
@end smallexample
! Here @samp{quit} is input to @value{GDBN}; the rest is output from
! @value{GDBN}. The three lines beginning @samp{^Z^Z} (where @samp{^Z}
! denotes a @samp{control-z} character) are annotations; the rest is
! output from @value{GDBN}.
@node Server Prefix
@section The Server Prefix
@cindex server prefix for annotations
! To issue a command to @value{GDBN} without affecting certain aspects of
! the state which is seen by users, prefix it with @samp{server }. This
! means that this command will not affect the command history, nor will it
! affect @value{GDBN}'s notion of which command to repeat if @key{RET} is
! pressed on a line by itself.
The server prefix does not affect the recording of values into the value
history; to print a value without recording it into the value history,
*************** use the @code{output} command instead of
*** 148,155 ****
@section Values
@cindex annotations for values
! When a value is printed in various contexts, @value{GDBN} uses annotations to
! delimit the value from the surrounding text.
@findex value-history-begin
@findex value-history-value
--- 152,159 ----
@section Values
@cindex annotations for values
! When a value is printed in various contexts, @value{GDBN} uses
! annotations to delimit the value from the surrounding text.
@findex value-history-begin
@findex value-history-value
*************** delimit the value from the surrounding t
*** 157,169 ****
If a value is printed using @code{print} and added to the value history,
the annotation looks like
! @example
^Z^Zvalue-history-begin @var{history-number} @var{value-flags}
@var{history-string}
^Z^Zvalue-history-value
@var{the-value}
^Z^Zvalue-history-end
! @end example
where @var{history-number} is the number it is getting in the value
history, @var{history-string} is a string, such as @samp{$5 = }, which
--- 161,173 ----
If a value is printed using @code{print} and added to the value history,
the annotation looks like
! @smallexample
^Z^Zvalue-history-begin @var{history-number} @var{value-flags}
@var{history-string}
^Z^Zvalue-history-value
@var{the-value}
^Z^Zvalue-history-end
! @end smallexample
where @var{history-number} is the number it is getting in the value
history, @var{history-string} is a string, such as @samp{$5 = }, which
*************** a value which can be dereferenced and @s
*** 176,186 ****
If the value is not added to the value history (it is an invalid float
or it is printed with the @code{output} command), the annotation is similar:
! @example
^Z^Zvalue-begin @var{value-flags}
@var{the-value}
^Z^Zvalue-end
! @end example
@findex arg-begin
@findex arg-name-end
--- 180,190 ----
If the value is not added to the value history (it is an invalid float
or it is printed with the @code{output} command), the annotation is similar:
! @smallexample
^Z^Zvalue-begin @var{value-flags}
@var{the-value}
^Z^Zvalue-end
! @end smallexample
@findex arg-begin
@findex arg-name-end
*************** or it is printed with the @code{output}
*** 189,195 ****
When @value{GDBN} prints an argument to a function (for example, in the output
from the @code{backtrace} command), it annotates it as follows:
! @example
^Z^Zarg-begin
@var{argument-name}
^Z^Zarg-name-end
--- 193,199 ----
When @value{GDBN} prints an argument to a function (for example, in the output
from the @code{backtrace} command), it annotates it as follows:
! @smallexample
^Z^Zarg-begin
@var{argument-name}
^Z^Zarg-name-end
*************** from the @code{backtrace} command), it a
*** 197,203 ****
^Z^Zarg-value @var{value-flags}
@var{the-value}
^Z^Zarg-end
! @end example
where @var{argument-name} is the name of the argument,
@var{separator-string} is text which separates the name from the value
--- 201,207 ----
^Z^Zarg-value @var{value-flags}
@var{the-value}
^Z^Zarg-end
! @end smallexample
where @var{argument-name} is the name of the argument,
@var{separator-string} is text which separates the name from the value
*************** for the user's benefit (such as @samp{=}
*** 211,217 ****
@findex field-end
When printing a structure, @value{GDBN} annotates it as follows:
! @example
^Z^Zfield-begin @var{value-flags}
@var{field-name}
^Z^Zfield-name-end
--- 215,221 ----
@findex field-end
When printing a structure, @value{GDBN} annotates it as follows:
! @smallexample
^Z^Zfield-begin @var{value-flags}
@var{field-name}
^Z^Zfield-name-end
*************** When printing a structure, @value{GDBN}
*** 219,225 ****
^Z^Zfield-value
@var{the-value}
^Z^Zfield-end
! @end example
where @var{field-name} is the name of the field, @var{separator-string}
is text which separates the name from the value for the user's benefit
--- 223,229 ----
^Z^Zfield-value
@var{the-value}
^Z^Zfield-end
! @end smallexample
where @var{field-name} is the name of the field, @var{separator-string}
is text which separates the name from the value for the user's benefit
*************** same meanings as in a @code{value-histor
*** 228,236 ****
When printing an array, @value{GDBN} annotates it as follows:
! @example
^Z^Zarray-section-begin @var{array-index} @var{value-flags}
! @end example
where @var{array-index} is the index of the first element being
annotated and @var{value-flags} has the same meaning as in a
--- 232,240 ----
When printing an array, @value{GDBN} annotates it as follows:
! @smallexample
^Z^Zarray-section-begin @var{array-index} @var{value-flags}
! @end smallexample
where @var{array-index} is the index of the first element being
annotated and @var{value-flags} has the same meaning as in a
*************** annotated and @var{value-flags} has the
*** 238,260 ****
of elements, where is element can be either a single element:
@findex elt
! @example
@samp{,} @var{whitespace} ; @r{omitted for the first element}
@var{the-value}
^Z^Zelt
! @end example
or a repeated element
@findex elt-rep
@findex elt-rep-end
! @example
@samp{,} @var{whitespace} ; @r{omitted for the first element}
@var{the-value}
^Z^Zelt-rep @var{number-of-repititions}
@var{repetition-string}
^Z^Zelt-rep-end
! @end example
In both cases, @var{the-value} is the output for the value of the
element and @var{whitespace} can contain spaces, tabs, and newlines. In
--- 242,264 ----
of elements, where is element can be either a single element:
@findex elt
! @smallexample
@samp{,} @var{whitespace} ; @r{omitted for the first element}
@var{the-value}
^Z^Zelt
! @end smallexample
or a repeated element
@findex elt-rep
@findex elt-rep-end
! @smallexample
@samp{,} @var{whitespace} ; @r{omitted for the first element}
@var{the-value}
^Z^Zelt-rep @var{number-of-repititions}
@var{repetition-string}
^Z^Zelt-rep-end
! @end smallexample
In both cases, @var{the-value} is the output for the value of the
element and @var{whitespace} can contain spaces, tabs, and newlines. In
*************** user that repitition is being depicted.
*** 267,275 ****
Once all the array elements have been output, the array annotation is
ended with
! @example
^Z^Zarray-section-end
! @end example
@node Frame Annotations
@section Frames
--- 271,279 ----
Once all the array elements have been output, the array annotation is
ended with
! @smallexample
^Z^Zarray-section-end
! @end smallexample
@node Frame Annotations
@section Frames
*************** to frames printed when @value{GDBN} stop
*** 282,291 ****
@findex frame-begin
The frame annotation begins with
! @example
^Z^Zframe-begin @var{level} @var{address}
@var{level-string}
! @end example
where @var{level} is the number of the frame (0 is the innermost frame,
and other frames have positive numbers), @var{address} is the address of
--- 286,295 ----
@findex frame-begin
The frame annotation begins with
! @smallexample
^Z^Zframe-begin @var{level} @var{address}
@var{level-string}
! @end smallexample
where @var{level} is the number of the frame (0 is the innermost frame,
and other frames have positive numbers), @var{address} is the address of
*************** designed to convey the level to the user
*** 295,303 ****
does not depend on the language). The frame ends with
@findex frame-end
! @example
^Z^Zframe-end
! @end example
Between these annotations is the main body of the frame, which can
consist of
--- 299,307 ----
does not depend on the language). The frame ends with
@findex frame-end
! @smallexample
^Z^Zframe-end
! @end smallexample
Between these annotations is the main body of the frame, which can
consist of
*************** consist of
*** 305,314 ****
@itemize @bullet
@item
@findex function-call
! @example
^Z^Zfunction-call
@var{function-call-string}
! @end example
where @var{function-call-string} is text designed to convey to the user
that this frame is associated with a function call made by @value{GDBN} to a
--- 309,318 ----
@itemize @bullet
@item
@findex function-call
! @smallexample
^Z^Zfunction-call
@var{function-call-string}
! @end smallexample
where @var{function-call-string} is text designed to convey to the user
that this frame is associated with a function call made by @value{GDBN} to a
*************** function in the program being debugged.
*** 316,325 ****
@item
@findex signal-handler-caller
! @example
^Z^Zsignal-handler-caller
@var{signal-handler-caller-string}
! @end example
where @var{signal-handler-caller-string} is text designed to convey to
the user that this frame is associated with whatever mechanism is used
--- 320,329 ----
@item
@findex signal-handler-caller
! @smallexample
^Z^Zsignal-handler-caller
@var{signal-handler-caller-string}
! @end smallexample
where @var{signal-handler-caller-string} is text designed to convey to
the user that this frame is associated with whatever mechanism is used
*************** A normal frame.
*** 334,345 ****
This can optionally (depending on whether this is thought of as
interesting information for the user to see) begin with
! @example
^Z^Zframe-address
@var{address}
^Z^Zframe-address-end
@var{separator-string}
! @end example
where @var{address} is the address executing in the frame (the same
address as in the @code{frame-begin} annotation, but printed in a form
--- 338,349 ----
This can optionally (depending on whether this is thought of as
interesting information for the user to see) begin with
! @smallexample
^Z^Zframe-address
@var{address}
^Z^Zframe-address-end
@var{separator-string}
! @end smallexample
where @var{address} is the address executing in the frame (the same
address as in the @code{frame-begin} annotation, but printed in a form
*************** benefit.
*** 352,363 ****
@findex frame-args
Then comes
! @example
^Z^Zframe-function-name
@var{function-name}
^Z^Zframe-args
@var{arguments}
! @end example
where @var{function-name} is the name of the function executing in the
frame, or @samp{??} if not known, and @var{arguments} are the arguments
--- 356,367 ----
@findex frame-args
Then comes
! @smallexample
^Z^Zframe-function-name
@var{function-name}
^Z^Zframe-args
@var{arguments}
! @end smallexample
where @var{function-name} is the name of the function executing in the
frame, or @samp{??} if not known, and @var{arguments} are the arguments
*************** individually as well, @pxref{Value Annot
*** 371,377 ****
@findex frame-source-end
If source information is available, a reference to it is then printed:
! @example
^Z^Zframe-source-begin
@var{source-intro-string}
^Z^Zframe-source-file
--- 375,381 ----
@findex frame-source-end
If source information is available, a reference to it is then printed:
! @smallexample
^Z^Zframe-source-begin
@var{source-intro-string}
^Z^Zframe-source-file
*************** If source information is available, a re
*** 381,387 ****
^Z^Zframe-source-line
@var{line-number}
^Z^Zframe-source-end
! @end example
where @var{source-intro-string} separates for the user's benefit the
reference from the text which precedes it, @var{filename} is the name of
--- 385,391 ----
^Z^Zframe-source-line
@var{line-number}
^Z^Zframe-source-end
! @end smallexample
where @var{source-intro-string} separates for the user's benefit the
reference from the text which precedes it, @var{filename} is the name of
*************** If @value{GDBN} prints some information
*** 393,402 ****
library, which load segment, etc.; currently only done on the RS/6000),
it is annotated with
! @example
^Z^Zframe-where
@var{information}
! @end example
Then, if source is to actually be displayed for this frame (for example,
this is not true for output from the @code{backtrace} command), then a
--- 397,406 ----
library, which load segment, etc.; currently only done on the RS/6000),
it is annotated with
! @smallexample
^Z^Zframe-where
@var{information}
! @end smallexample
Then, if source is to actually be displayed for this frame (for example,
this is not true for output from the @code{backtrace} command), then a
*************** output, not in addition.
*** 419,425 ****
When @value{GDBN} is told to display something using the @code{display} command,
the results of the display are annotated:
! @example
^Z^Zdisplay-begin
@var{number}
^Z^Zdisplay-number-end
--- 423,429 ----
When @value{GDBN} is told to display something using the @code{display} command,
the results of the display are annotated:
! @smallexample
^Z^Zdisplay-begin
@var{number}
^Z^Zdisplay-number-end
*************** the results of the display are annotated
*** 433,439 ****
^Z^Zdisplay-value
@var{value}
^Z^Zdisplay-end
! @end example
where @var{number} is the number of the display, @var{number-separator}
is intended to separate the number from what follows for the user,
--- 437,443 ----
^Z^Zdisplay-value
@var{value}
^Z^Zdisplay-end
! @end smallexample
where @var{number} is the number of the display, @var{number-separator}
is intended to separate the number from what follows for the user,
*************** annotation which denotes the end of any
*** 459,469 ****
associated with the input. For example, the @code{prompt} input type
features the following annotations:
! @example
^Z^Zpre-prompt
^Z^Zprompt
^Z^Zpost-prompt
! @end example
The input types are
--- 463,473 ----
associated with the input. For example, the @code{prompt} input type
features the following annotations:
! @smallexample
^Z^Zpre-prompt
^Z^Zprompt
^Z^Zpost-prompt
! @end smallexample
The input types are
*************** presence of annotations.
*** 508,523 ****
@cindex annotations for errors, warnings and interrupts
@findex quit
! @example
^Z^Zquit
! @end example
This annotation occurs right before @value{GDBN} responds to an interrupt.
@findex error
! @example
^Z^Zerror
! @end example
This annotation occurs right before @value{GDBN} responds to an error.
--- 512,527 ----
@cindex annotations for errors, warnings and interrupts
@findex quit
! @smallexample
^Z^Zquit
! @end smallexample
This annotation occurs right before @value{GDBN} responds to an interrupt.
@findex error
! @smallexample
^Z^Zerror
! @end smallexample
This annotation occurs right before @value{GDBN} responds to an error.
*************** to the top level.
*** 532,540 ****
@findex error-begin
A quit or error annotation may be preceded by
! @example
^Z^Zerror-begin
! @end example
Any output between that and the quit or error annotation is the error
message.
--- 536,544 ----
@findex error-begin
A quit or error annotation may be preceded by
! @smallexample
^Z^Zerror-begin
! @end smallexample
Any output between that and the quit or error annotation is the error
message.
*************** The output from the @code{info breakpoin
*** 551,561 ****
@findex breakpoints-headers
@findex breakpoints-table
! @example
^Z^Zbreakpoints-headers
@var{header-entry}
^Z^Zbreakpoints-table
! @end example
where @var{header-entry} has the same syntax as an entry (see below) but
instead of containing data, it contains strings which are intended to
--- 555,565 ----
@findex breakpoints-headers
@findex breakpoints-table
! @smallexample
^Z^Zbreakpoints-headers
@var{header-entry}
^Z^Zbreakpoints-table
! @end smallexample
where @var{header-entry} has the same syntax as an entry (see below) but
instead of containing data, it contains strings which are intended to
*************** of:
*** 566,572 ****
@findex record
@findex field
! @example
^Z^Zrecord
^Z^Zfield 0
@var{number}
--- 570,576 ----
@findex record
@findex field
! @smallexample
^Z^Zrecord
^Z^Zfield 0
@var{number}
*************** of:
*** 588,594 ****
@var{ignore-count}
^Z^Zfield 9
@var{commands}
! @end example
Note that @var{address} is intended for user consumption---the syntax
varies depending on the language.
--- 592,598 ----
@var{ignore-count}
^Z^Zfield 9
@var{commands}
! @end smallexample
Note that @var{address} is intended for user consumption---the syntax
varies depending on the language.
*************** varies depending on the language.
*** 596,604 ****
The output ends with
@findex breakpoints-table-end
! @example
^Z^Zbreakpoints-table-end
! @end example
@node Invalidation
@section Invalidation Notices
--- 600,608 ----
The output ends with
@findex breakpoints-table-end
! @smallexample
^Z^Zbreakpoints-table-end
! @end smallexample
@node Invalidation
@section Invalidation Notices
*************** deleted a breakpoint.
*** 630,644 ****
When the program starts executing due to a @value{GDBN} command such as
@code{step} or @code{continue},
! @example
^Z^Zstarting
! @end example
is output. When the program stops,
! @example
^Z^Zstopped
! @end example
is output. Before the @code{stopped} annotation, a variety of
annotations describe how the program stopped.
--- 634,648 ----
When the program starts executing due to a @value{GDBN} command such as
@code{step} or @code{continue},
! @smallexample
^Z^Zstarting
! @end smallexample
is output. When the program stops,
! @smallexample
^Z^Zstopped
! @end smallexample
is output. Before the @code{stopped} annotation, a variety of
annotations describe how the program stopped.
*************** successful exit, otherwise nonzero).
*** 658,664 ****
The program exited with a signal. After the @code{^Z^Zsignalled}, the
annotation continues:
! @example
@var{intro-text}
^Z^Zsignal-name
@var{name}
--- 662,668 ----
The program exited with a signal. After the @code{^Z^Zsignalled}, the
annotation continues:
! @smallexample
@var{intro-text}
^Z^Zsignal-name
@var{name}
*************** annotation continues:
*** 668,674 ****
@var{string}
^Z^Zsignal-string-end
@var{end-text}
! @end example
where @var{name} is the name of the signal, such as @code{SIGILL} or
@code{SIGSEGV}, and @var{string} is the explanation of the signal, such
--- 672,678 ----
@var{string}
^Z^Zsignal-string-end
@var{end-text}
! @end smallexample
where @var{name} is the name of the signal, such as @code{SIGILL} or
@code{SIGSEGV}, and @var{string} is the explanation of the signal, such
*************** The program hit watchpoint number @var{n
*** 698,706 ****
@findex source
The following annotation is used instead of displaying source code:
! @example
^Z^Zsource @var{filename}:@var{line}:@var{character}:@var{middle}:@var{addr}
! @end example
where @var{filename} is an absolute file name indicating which source
file, @var{line} is the line number within that file (where 1 is the
--- 702,710 ----
@findex source
The following annotation is used instead of displaying source code:
! @smallexample
^Z^Zsource @var{filename}:@var{line}:@var{character}:@var{middle}:@var{addr}
! @end smallexample
where @var{filename} is an absolute file name indicating which source
file, @var{line} is the line number within that file (where 1 is the
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.8
diff -p -r1.8 gdb.texinfo
*** gdb.texinfo 2000/03/28 02:25:13 1.8
--- gdb.texinfo 2000/03/28 16:33:52
***************
*** 1,5 ****
\input texinfo @c -*-texinfo-*-
! @c Copyright 1988-1999
@c Free Software Foundation, Inc.
@c
@c %**start of header
--- 1,5 ----
\input texinfo @c -*-texinfo-*-
! @c Copyright 1988-2000
@c Free Software Foundation, Inc.
@c
@c %**start of header
***************
*** 25,39 ****
@syncodeindex vr cp
@c !!set GDB manual's edition---not the same as GDB version!
! @set EDITION Seventh
@c !!set GDB manual's revision date
! @set DATE February 1999
! @c THIS MANUAL REQUIRES TEXINFO-2 macros and info-makers to format properly.
@c This is a dir.info fragment to support semi-automated addition of
! @c manuals to an info tree. zoo@cygnus.com is developing this facility.
@dircategory Programming & development tools.
@direntry
* Gdb: (gdb). The @sc{gnu} debugger.
--- 25,39 ----
@syncodeindex vr cp
@c !!set GDB manual's edition---not the same as GDB version!
! @set EDITION Eighth
@c !!set GDB manual's revision date
! @set DATE March 2000
! @c THIS MANUAL REQUIRES TEXINFO 3.12 OR LATER.
@c This is a dir.info fragment to support semi-automated addition of
! @c manuals to an info tree.
@dircategory Programming & development tools.
@direntry
* Gdb: (gdb). The @sc{gnu} debugger.
*************** This is the @value{EDITION} Edition, @va
*** 47,53 ****
of @cite{Debugging with @value{GDBN}: the @sc{gnu} Source-Level Debugger}
for @value{GDBN} Version @value{GDBVN}.
! Copyright (C) 1988-1999 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
--- 47,53 ----
of @cite{Debugging with @value{GDBN}: the @sc{gnu} Source-Level Debugger}
for @value{GDBN} Version @value{GDBVN}.
! Copyright (C) 1988-2000 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
*************** into another language, under the above c
*** 85,101 ****
}
@end tex
- @c ISBN seems to be wrong...
-
@vskip 0pt plus 1filll
! Copyright @copyright{} 1988-1999 Free Software Foundation, Inc.
@sp 2
Published by the Free Software Foundation @*
59 Temple Place - Suite 330, @*
Boston, MA 02111-1307 USA @*
! Printed copies are available for $20 each. @*
! ISBN 1-882114-11-6 @*
!
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
are preserved on all copies.
--- 85,98 ----
}
@end tex
@vskip 0pt plus 1filll
! Copyright @copyright{} 1988-2000 Free Software Foundation, Inc.
@sp 2
Published by the Free Software Foundation @*
59 Temple Place - Suite 330, @*
Boston, MA 02111-1307 USA @*
! ISBN 1-882114-77-9 @*
!
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
are preserved on all copies.
*************** into another language, under the above c
*** 110,127 ****
@end titlepage
@page
-
- @node Top, Summary, (dir), (dir)
@ifinfo
@top Debugging with @value{GDBN}
This file describes @value{GDBN}, the @sc{gnu} symbolic debugger.
This is the @value{EDITION} Edition, @value{DATE}, for @value{GDBN} Version
@value{GDBVN}.
! Copyright (C) 1988-1999 Free Software Foundation, Inc.
@end ifinfo
@menu
* Summary:: Summary of @value{GDBN}
* Sample Session:: A sample @value{GDBN} session
--- 107,173 ----
@end titlepage
@page
@ifinfo
+ @node Top, Summary, (dir), (dir)
+
@top Debugging with @value{GDBN}
This file describes @value{GDBN}, the @sc{gnu} symbolic debugger.
This is the @value{EDITION} Edition, @value{DATE}, for @value{GDBN} Version
@value{GDBVN}.
+
+ Copyright (C) 1988-2000 Free Software Foundation, Inc.
+
+ @menu
+ * Summary:: Summary of @value{GDBN}
+ * Sample Session:: A sample @value{GDBN} session
+
+ * Invocation:: Getting in and out of @value{GDBN}
+ * Commands:: @value{GDBN} commands
+ * Running:: Running programs under @value{GDBN}
+ * Stopping:: Stopping and continuing
+ * Stack:: Examining the stack
+ * Source:: Examining source files
+ * Data:: Examining data
! * Languages:: Using @value{GDBN} with different languages
!
! * Symbols:: Examining the symbol table
! * Altering:: Altering execution
! * GDB Files:: @value{GDBN} files
! * Targets:: Specifying a debugging target
! * Configurations:: Configuration-specific information
! * Controlling GDB:: Controlling @value{GDBN}
! * Sequences:: Canned sequences of commands
! * Emacs:: Using @value{GDBN} under @sc{gnu} Emacs
! * Annotations:: @value{GDBN}'s annotation interface.
!
! * GDB Bugs:: Reporting bugs in @value{GDBN}
! * Formatting Documentation:: How to format and print @value{GDBN} documentation
!
! * Command Line Editing:: Command Line Editing
! * Using History Interactively:: Using History Interactively
! * Installing GDB:: Installing GDB
! * Index:: Index
! @end menu
!
@end ifinfo
+
+ @c the replication sucks, but this avoids a texinfo 3.12 lameness
+
+ @ifhtml
+ @node Top
+
+ @top Debugging with @value{GDBN}
+
+ This file describes @value{GDBN}, the @sc{gnu} symbolic debugger.
+
+ This is the @value{EDITION} Edition, @value{DATE}, for @value{GDBN} Version
+ @value{GDBVN}.
+
+ Copyright (C) 1988-2000 Free Software Foundation, Inc.
+
@menu
* Summary:: Summary of @value{GDBN}
* Sample Session:: A sample @value{GDBN} session
*************** Copyright (C) 1988-1999 Free Software Fo
*** 144,150 ****
* Controlling GDB:: Controlling @value{GDBN}
* Sequences:: Canned sequences of commands
* Emacs:: Using @value{GDBN} under @sc{gnu} Emacs
! * Annotations:: @value{GDBN}'s annotations interface.
* GDB Bugs:: Reporting bugs in @value{GDBN}
* Formatting Documentation:: How to format and print @value{GDBN} documentation
--- 190,196 ----
* Controlling GDB:: Controlling @value{GDBN}
* Sequences:: Canned sequences of commands
* Emacs:: Using @value{GDBN} under @sc{gnu} Emacs
! * Annotations:: @value{GDBN}'s annotation interface.
* GDB Bugs:: Reporting bugs in @value{GDBN}
* Formatting Documentation:: How to format and print @value{GDBN} documentation
*************** Copyright (C) 1988-1999 Free Software Fo
*** 155,161 ****
* Index:: Index
@end menu
! @node Summary, Sample Session, Top, Top
@unnumbered Summary of @value{GDBN}
The purpose of a debugger such as @value{GDBN} is to allow you to see what is
--- 201,209 ----
* Index:: Index
@end menu
! @end ifhtml
!
! @node Summary
@unnumbered Summary of @value{GDBN}
The purpose of a debugger such as @value{GDBN} is to allow you to see what is
*************** underscore.
*** 205,211 ****
* Contributors:: Contributors to GDB
@end menu
! @node Free Software, Contributors, Summary, Summary
@unnumberedsec Free software
@value{GDBN} is @dfn{free software}, protected by the @sc{gnu}
--- 253,259 ----
* Contributors:: Contributors to GDB
@end menu
! @node Free Software
@unnumberedsec Free software
@value{GDBN} is @dfn{free software}, protected by the @sc{gnu}
*************** Fundamentally, the General Public Licens
*** 221,227 ****
you have these freedoms and that you cannot take these freedoms away
from anyone else.
! @node Contributors, , Free Software, Summary
@unnumberedsec Contributors to @value{GDBN}
Richard Stallman was the original author of @value{GDBN}, and of many
--- 269,275 ----
you have these freedoms and that you cannot take these freedoms away
from anyone else.
! @node Contributors
@unnumberedsec Contributors to @value{GDBN}
Richard Stallman was the original author of @value{GDBN}, and of many
*************** Thomas, Michael Tiemann, Tom Tromey, Ron
*** 360,366 ****
Zuhn have made contributions both large and small.
! @node Sample Session, Invocation, Summary, Top
@chapter A Sample @value{GDBN} Session
You can use this manual at your leisure to read all about @value{GDBN}.
--- 408,414 ----
Zuhn have made contributions both large and small.
! @node Sample Session
@chapter A Sample @value{GDBN} Session
You can use this manual at your leisure to read all about @value{GDBN}.
*************** session with the @value{GDBN} @code{quit
*** 630,636 ****
(@value{GDBP}) @b{quit}
@end smallexample
! @node Invocation, Commands, Sample Session, Top
@chapter Getting In and Out of @value{GDBN}
This chapter discusses how to start @value{GDBN}, and how to get out of it.
--- 678,684 ----
(@value{GDBP}) @b{quit}
@end smallexample
! @node Invocation
@chapter Getting In and Out of @value{GDBN}
This chapter discusses how to start @value{GDBN}, and how to get out of it.
*************** type @kbd{quit} or @kbd{C-d} to exit.
*** 648,654 ****
* Shell Commands:: How to use shell commands inside @value{GDBN}
@end menu
! @node Invoking GDB, Quitting GDB, Invocation, Invocation
@section Invoking @value{GDBN}
Invoke @value{GDBN} by running the program @code{@value{GDBP}}. Once started,
--- 696,702 ----
* Shell Commands:: How to use shell commands inside @value{GDBN}
@end menu
! @node Invoking GDB
@section Invoking @value{GDBN}
Invoke @value{GDBN} by running the program @code{@value{GDBP}}. Once started,
*************** in sequential order. The order makes a
*** 725,731 ****
* Mode Options:: Choosing modes
@end menu
! @node File Options, Mode Options, Invoking GDB, Invoking GDB
@subsection Choosing files
When @value{GDBN} starts, it reads any arguments other than options as
--- 773,779 ----
* Mode Options:: Choosing modes
@end menu
! @node File Options
@subsection Choosing files
When @value{GDBN} starts, it reads any arguments other than options as
*************** but build a @file{.syms} file for future
*** 833,839 ****
gdb -batch -nx -mapped -readnow programname
@end example
! @node Mode Options, , File Options, Invoking GDB
@subsection Choosing modes
You can run @value{GDBN} in various alternative modes---for example, in
--- 881,887 ----
gdb -batch -nx -mapped -readnow programname
@end example
! @node Mode Options
@subsection Choosing modes
You can run @value{GDBN} in various alternative modes---for example, in
*************** no-warranty blurb, and exit.
*** 1014,1020 ****
@end table
! @node Quitting GDB, Shell Commands, Invoking GDB, Invocation
@section Quitting @value{GDBN}
@cindex exiting @value{GDBN}
@cindex leaving @value{GDBN}
--- 1062,1068 ----
@end table
! @node Quitting GDB
@section Quitting @value{GDBN}
@cindex exiting @value{GDBN}
@cindex leaving @value{GDBN}
*************** If you have been using @value{GDBN} to c
*** 1042,1048 ****
device, you can release it with the @code{detach} command
(@pxref{Attach, ,Debugging an already-running process}).
! @node Shell Commands, , Quitting GDB, Invocation
@section Shell commands
If you need to execute occasional shell commands during your
--- 1090,1096 ----
device, you can release it with the @code{detach} command
(@pxref{Attach, ,Debugging an already-running process}).
! @node Shell Commands
@section Shell commands
If you need to execute occasional shell commands during your
*************** Execute the @code{make} program with the
*** 1071,1077 ****
arguments. This is equivalent to @samp{shell make @var{make-args}}.
@end table
! @node Commands, Running, Invocation, Top
@chapter @value{GDBN} Commands
You can abbreviate a @value{GDBN} command to the first few letters of the command
--- 1119,1125 ----
arguments. This is equivalent to @samp{shell make @var{make-args}}.
@end table
! @node Commands
@chapter @value{GDBN} Commands
You can abbreviate a @value{GDBN} command to the first few letters of the command
*************** show you the alternatives available, if
*** 1086,1092 ****
* Help:: How to ask @value{GDBN} for help
@end menu
! @node Command Syntax, Completion, Commands, Commands
@section Command syntax
A @value{GDBN} command is a single line of input. There is no limit on
--- 1134,1140 ----
* Help:: How to ask @value{GDBN} for help
@end menu
! @node Command Syntax
@section Command syntax
A @value{GDBN} command is a single line of input. There is no limit on
*************** Any text from a @kbd{#} to the end of th
*** 1129,1135 ****
nothing. This is useful mainly in command files (@pxref{Command
Files,,Command files}).
! @node Completion, Help, Command Syntax, Commands
@section Command completion
@cindex completion
--- 1177,1183 ----
nothing. This is useful mainly in command files (@pxref{Command
Files,,Command files}).
! @node Completion
@section Command completion
@cindex completion
*************** overload-resolution off} to disable over
*** 1248,1254 ****
see @ref{Debugging C plus plus, ,@value{GDBN} features for C++}.
! @node Help, , Completion, Commands
@section Getting help
@cindex online documentation
@kindex help
--- 1296,1302 ----
see @ref{Debugging C plus plus, ,@value{GDBN} features for C++}.
! @node Help
@section Getting help
@cindex online documentation
@kindex help
*************** apropos reload
*** 1331,1340 ****
@noindent results in:
@smallexample
! @group
! set symbol-reloading -- Set dynamic symbol table reloading multiple times in one run
! show symbol-reloading -- Show dynamic symbol table reloading multiple times in one run
! @end group
@end smallexample
@kindex complete
--- 1379,1390 ----
@noindent results in:
@smallexample
! @c @group
! set symbol-reloading -- Set dynamic symbol table reloading
! multiple times in one run
! show symbol-reloading -- Show dynamic symbol table reloading
! multiple times in one run
! @c @end group
@end smallexample
@kindex complete
*************** if your version of @value{GDBN} comes wi
*** 1433,1439 ****
@end table
! @node Running, Stopping, Commands, Top
@chapter Running Programs Under @value{GDBN}
When you run a program under @value{GDBN}, you must first generate
--- 1483,1489 ----
@end table
! @node Running
@chapter Running Programs Under @value{GDBN}
When you run a program under @value{GDBN}, you must first generate
*************** kill a child process.
*** 1459,1465 ****
* Processes:: Debugging programs with multiple processes
@end menu
! @node Compilation, Starting, Running, Running
@section Compiling for debugging
In order to debug a program effectively, you need to generate
--- 1509,1515 ----
* Processes:: Debugging programs with multiple processes
@end menu
! @node Compilation
@section Compiling for debugging
In order to debug a program effectively, you need to generate
*************** Older versions of the @sc{gnu} C compile
*** 1500,1506 ****
format; if your @sc{gnu} C compiler has this option, do not use it.
@need 2000
! @node Starting, Arguments, Compilation, Running
@section Starting your program
@cindex starting
@cindex running
--- 1550,1556 ----
format; if your @sc{gnu} C compiler has this option, do not use it.
@need 2000
! @node Starting
@section Starting your program
@cindex starting
@cindex running
*************** time @value{GDBN} read its symbols, @val
*** 1576,1582 ****
table, and reads it again. When it does this, @value{GDBN} tries to retain
your current breakpoints.
! @node Arguments, Environment, Starting, Running
@section Your program's arguments
@cindex arguments (to your program)
--- 1626,1632 ----
table, and reads it again. When it does this, @value{GDBN} tries to retain
your current breakpoints.
! @node Arguments
@section Your program's arguments
@cindex arguments (to your program)
*************** it again without arguments.
*** 1610,1616 ****
Show the arguments to give your program when it is started.
@end table
! @node Environment, Working Directory, Arguments, Running
@section Your program's environment
@cindex environment (of your program)
--- 1660,1666 ----
Show the arguments to give your program when it is started.
@end table
! @node Environment
@section Your program's environment
@cindex environment (of your program)
*************** your program. You may wish to move sett
*** 1693,1699 ****
files that are only run when you sign on, such as @file{.login} or
@file{.profile}.
! @node Working Directory, Input/Output, Environment, Running
@section Your program's working directory
@cindex working directory (of your program)
--- 1743,1749 ----
files that are only run when you sign on, such as @file{.login} or
@file{.profile}.
! @node Working Directory
@section Your program's working directory
@cindex working directory (of your program)
*************** Set the @value{GDBN} working directory t
*** 1717,1723 ****
Print the @value{GDBN} working directory.
@end table
! @node Input/Output, Attach, Working Directory, Running
@section Your program's input and output
@cindex redirection
--- 1767,1773 ----
Print the @value{GDBN} working directory.
@end table
! @node Input/Output
@section Your program's input and output
@cindex redirection
*************** When you use the @code{tty} command or r
*** 1771,1777 ****
command, only the input @emph{for your program} is affected. The input
for @value{GDBN} still comes from your terminal.
! @node Attach, Kill Process, Input/Output, Running
@section Debugging an already-running process
@kindex attach
@cindex attach
--- 1821,1827 ----
command, only the input @emph{for your program} is affected. The input
for @value{GDBN} still comes from your terminal.
! @node Attach
@section Debugging an already-running process
@kindex attach
@cindex attach
*************** control whether or not you need to confi
*** 1827,1833 ****
confirm} command (@pxref{Messages/Warnings, ,Optional warnings and
messages}).
! @node Kill Process, Threads, Attach, Running
@section Killing the child process
@table @code
--- 1877,1883 ----
confirm} command (@pxref{Messages/Warnings, ,Optional warnings and
messages}).
! @node Kill Process
@section Killing the child process
@table @code
*************** next type @code{run}, @value{GDBN} notic
*** 1852,1858 ****
reads the symbol table again (while trying to preserve your current
breakpoint settings).
! @node Threads, Processes, Kill Process, Running
@section Debugging programs with multiple threads
@cindex threads of execution
--- 1902,1908 ----
reads the symbol table again (while trying to preserve your current
breakpoint settings).
! @node Threads
@section Debugging programs with multiple threads
@cindex threads of execution
*************** For example,
*** 2017,2025 ****
@example
(@value{GDBP}) info threads
! * 3 system thread 26607 worker (wptr=0x7b09c318 "@@") at quicksort.c:137
! 2 system thread 26606 0x7b0030d8 in __ksleep () from /usr/lib/libc.2
! 1 system thread 27905 0x7b003498 in _brk () from /usr/lib/libc.2
@end example
@table @code
--- 2067,2078 ----
@example
(@value{GDBP}) info threads
! * 3 system thread 26607 worker (wptr=0x7b09c318 "@@") \@*
! at quicksort.c:137
! 2 system thread 26606 0x7b0030d8 in __ksleep () \@*
! from /usr/lib/libc.2
! 1 system thread 27905 0x7b003498 in _brk () \@*
! from /usr/lib/libc.2
@end example
@table @code
*************** programs with multiple threads.
*** 2069,2075 ****
@xref{Set Watchpoints,,Setting watchpoints}, for information about
watchpoints in programs with multiple threads.
! @node Processes, , Threads, Running
@section Debugging programs with multiple processes
@cindex fork, debugging programs which call
--- 2122,2128 ----
@xref{Set Watchpoints,,Setting watchpoints}, for information about
watchpoints in programs with multiple threads.
! @node Processes
@section Debugging programs with multiple processes
@cindex fork, debugging programs which call
*************** You can use the @code{catch} command to
*** 2146,2152 ****
a @code{fork}, @code{vfork}, or @code{exec} call is made. @xref{Set
Catchpoints, ,Setting catchpoints}.
! @node Stopping, Stack, Running, Top
@chapter Stopping and Continuing
The principal purposes of using a debugger are so that you can stop your
--- 2199,2205 ----
a @code{fork}, @code{vfork}, or @code{exec} call is made. @xref{Set
Catchpoints, ,Setting catchpoints}.
! @node Stopping
@chapter Stopping and Continuing
The principal purposes of using a debugger are so that you can stop your
*************** running or not, what process it is, and
*** 2175,2181 ****
* Thread Stops:: Stopping and starting multi-thread programs
@end menu
! @node Breakpoints, Continuing and Stepping, Stopping, Stopping
@section Breakpoints, watchpoints, and catchpoints
@cindex breakpoints
--- 2228,2234 ----
* Thread Stops:: Stopping and starting multi-thread programs
@end menu
! @node Breakpoints
@section Breakpoints, watchpoints, and catchpoints
@cindex breakpoints
*************** all breakpoint in that range are operate
*** 2249,2255 ****
* Error in Breakpoints:: ``Cannot insert breakpoints''
@end menu
! @node Set Breaks, Set Watchpoints, Breakpoints, Breakpoints
@subsection Setting breakpoints
@c FIXME LMB what does GDB do if no code on line of breakpt?
--- 2302,2308 ----
* Error in Breakpoints:: ``Cannot insert breakpoints''
@end menu
! @node Set Breaks
@subsection Setting breakpoints
@c FIXME LMB what does GDB do if no code on line of breakpt?
*************** Shared library events.
*** 2481,2487 ****
@end table
! @node Set Watchpoints, Set Catchpoints, Set Breaks, Breakpoints
@subsection Setting watchpoints
@cindex setting watchpoints
--- 2534,2540 ----
@end table
! @node Set Watchpoints
@subsection Setting watchpoints
@cindex setting watchpoints
*************** when a non-current thread's activity cha
*** 2624,2630 ****
watchpoints, in contrast, watch an expression in all threads.)
@end quotation
! @node Set Catchpoints, Delete Breaks, Set Watchpoints, Breakpoints
@subsection Setting catchpoints
@cindex catchpoints, setting
@cindex exception handlers
--- 2677,2683 ----
watchpoints, in contrast, watch an expression in all threads.)
@end quotation
! @node Set Catchpoints
@subsection Setting catchpoints
@cindex catchpoints, setting
@cindex exception handlers
*************** breakpoints to stop your program when an
*** 2732,2738 ****
raised.
! @node Delete Breaks, Disabling, Set Catchpoints, Breakpoints
@subsection Deleting breakpoints
@cindex clearing breakpoints, watchpoints, catchpoints
--- 2785,2791 ----
raised.
! @node Delete Breaks
@subsection Deleting breakpoints
@cindex clearing breakpoints, watchpoints, catchpoints
*************** breakpoints (@value{GDBN} asks confirmat
*** 2777,2783 ****
confirm off}). You can abbreviate this command as @code{d}.
@end table
! @node Disabling, Conditions, Delete Breaks, Breakpoints
@subsection Disabling breakpoints
@kindex disable breakpoints
--- 2830,2836 ----
confirm off}). You can abbreviate this command as @code{d}.
@end table
! @node Disabling
@subsection Disabling breakpoints
@kindex disable breakpoints
*************** breakpoint of its own, but it does not c
*** 2850,2856 ****
breakpoints; see @ref{Continuing and Stepping, ,Continuing and
stepping}.)
! @node Conditions, Break Commands, Disabling, Breakpoints
@subsection Break conditions
@cindex conditional breakpoints
@cindex breakpoint conditions
--- 2903,2909 ----
breakpoints; see @ref{Continuing and Stepping, ,Continuing and
stepping}.)
! @node Conditions
@subsection Break conditions
@cindex conditional breakpoints
@cindex breakpoint conditions
*************** variables}.
*** 2967,2973 ****
Ignore counts apply to breakpoints, watchpoints, and catchpoints.
! @node Break Commands, Breakpoint Menus, Conditions, Breakpoints
@subsection Breakpoint command lists
@cindex breakpoint commands
--- 3020,3026 ----
Ignore counts apply to breakpoints, watchpoints, and catchpoints.
! @node Break Commands
@subsection Breakpoint command lists
@cindex breakpoint commands
*************** cont
*** 3048,3054 ****
end
@end example
! @node Breakpoint Menus, Error in Breakpoints, Break Commands, Breakpoints
@subsection Breakpoint menus
@cindex overloading
@cindex symbol overloading
--- 3101,3107 ----
end
@end example
! @node Breakpoint Menus
@subsection Breakpoint menus
@cindex overloading
@cindex symbol overloading
*************** Use the "delete" command to delete unwan
*** 3095,3101 ****
@end smallexample
@c @ifclear BARETARGET
! @node Error in Breakpoints, , Breakpoint Menus, Breakpoints
@subsection ``Cannot insert breakpoints''
@c
@c FIXME!! 14/6/95 Is there a real example of this? Let's use it.
--- 3148,3154 ----
@end smallexample
@c @ifclear BARETARGET
! @node Error in Breakpoints
@subsection ``Cannot insert breakpoints''
@c
@c FIXME!! 14/6/95 Is there a real example of this? Let's use it.
*************** When this message is printed, you need t
*** 3148,3154 ****
hardware-assisted breakpoints and watchpoints, and then continue.
! @node Continuing and Stepping, Signals, Breakpoints, Stopping
@section Continuing and stepping
@cindex stepping
--- 3201,3207 ----
hardware-assisted breakpoints and watchpoints, and then continue.
! @node Continuing and Stepping
@section Continuing and stepping
@cindex stepping
*************** proceed until the function returns.
*** 3350,3356 ****
An argument is a repeat count, as in @code{next}.
@end table
! @node Signals, Thread Stops, Continuing and Stepping, Stopping
@section Signals
@cindex signals
--- 3403,3409 ----
An argument is a repeat count, as in @code{next}.
@end table
! @node Signals
@section Signals
@cindex signals
*************** a result of the fatal signal once it saw
*** 3446,3452 ****
you can continue with @samp{signal 0}. @xref{Signaling, ,Giving your
program a signal}.
! @node Thread Stops, , Signals, Stopping
@section Stopping and starting multi-thread programs
When your program has multiple threads (@pxref{Threads,, Debugging
--- 3499,3505 ----
you can continue with @samp{signal 0}. @xref{Signaling, ,Giving your
program a signal}.
! @node Thread Stops
@section Stopping and starting multi-thread programs
When your program has multiple threads (@pxref{Threads,, Debugging
*************** Display the current scheduler locking mo
*** 3531,3537 ****
@end table
! @node Stack, Source, Stopping, Top
@chapter Examining the Stack
When your program has stopped, the first thing you need to know is where it
--- 3584,3590 ----
@end table
! @node Stack
@chapter Examining the Stack
When your program has stopped, the first thing you need to know is where it
*************** currently executing frame and describes
*** 3570,3576 ****
@end menu
! @node Frames, Backtrace, Stack, Stack
@section Stack frames
@cindex frame, definition
--- 3623,3629 ----
@end menu
! @node Frames
@section Stack frames
@cindex frame, definition
*************** and so on upward. These numbers do not
*** 3608,3618 ****
they are assigned by @value{GDBN} to give you a way of designating stack
frames in @value{GDBN} commands.
! @c below produces an acceptable overful hbox. --mew 13aug1993
@cindex frameless execution
Some compilers provide a way to compile functions so that they operate
! without stack frames. (For example, the @code{@value{GCC}} option
! @samp{-fomit-frame-pointer} generates functions without a frame.)
This is occasionally done with heavily used library functions to save
the frame setup time. @value{GDBN} has limited facilities for dealing
with these function invocations. If the innermost function invocation
--- 3661,3675 ----
they are assigned by @value{GDBN} to give you a way of designating stack
frames in @value{GDBN} commands.
! @c The -fomit-frame-pointer below perennially causes hbox overflow
! @c underflow problems.
@cindex frameless execution
Some compilers provide a way to compile functions so that they operate
! without stack frames. (For example, the @value{GCC} option
! @example
! @samp{-fomit-frame-pointer}
! @end example
! generates functions without a frame.)
This is occasionally done with heavily used library functions to save
the frame setup time. @value{GDBN} has limited facilities for dealing
with these function invocations. If the innermost function invocation
*************** to another without printing the frame.
*** 3636,3642 ****
@code{frame}.
@end table
! @node Backtrace, Selection, Frames, Stack
@section Backtraces
@cindex backtraces
--- 3693,3699 ----
@code{frame}.
@end table
! @node Backtrace
@section Backtraces
@cindex backtraces
*************** The display for frame zero does not begi
*** 3699,3705 ****
value, indicating that your program has stopped at the beginning of the
code for line @code{993} of @code{builtin.c}.
! @node Selection, Frame Info, Backtrace, Stack
@section Selecting a frame
Most commands for examining the stack and other data in your program work on
--- 3756,3762 ----
value, indicating that your program has stopped at the beginning of the
code for line @code{993} of @code{builtin.c}.
! @node Selection
@section Selecting a frame
Most commands for examining the stack and other data in your program work on
*************** in @value{GDBN} command scripts, where t
*** 3785,3791 ****
distracting.
@end table
! @node Frame Info, , Selection, Stack
@section Information about a frame
There are several other commands to print information about the selected
--- 3842,3848 ----
distracting.
@end table
! @node Frame Info
@section Information about a frame
There are several other commands to print information about the selected
*************** exception handlers, visit the associated
*** 3861,3867 ****
@end table
! @node Source, Data, Stack, Top
@chapter Examining Source Files
@value{GDBN} can print parts of your program's source, since the debugging
--- 3918,3924 ----
@end table
! @node Source
@chapter Examining Source Files
@value{GDBN} can print parts of your program's source, since the debugging
*************** prefer to use Emacs facilities to view s
*** 3883,3889 ****
* Machine Code:: Source and machine code
@end menu
! @node List, Search, Source, Source
@section Printing source lines
@kindex list
--- 3940,3946 ----
* Machine Code:: Source and machine code
@end menu
! @node List
@section Printing source lines
@kindex list
*************** Specifies the line containing the progra
*** 4000,4006 ****
@var{address} may be any expression.
@end table
! @node Search, Source Path, List, Source
@section Searching source files
@cindex searching
@kindex reverse-search
--- 4057,4063 ----
@var{address} may be any expression.
@end table
! @node Search
@section Searching source files
@cindex searching
@kindex reverse-search
*************** for @var{regexp}. It lists the line tha
*** 4026,4032 ****
this command as @code{rev}.
@end table
! @node Source Path, Machine Code, Search, Source
@section Specifying source directories
@cindex source path
--- 4083,4089 ----
this command as @code{rev}.
@end table
! @node Source Path
@section Specifying source directories
@cindex source path
*************** directories you want in the source path.
*** 4109,4115 ****
directories in one command.
@end enumerate
! @node Machine Code, , Source Path, Source
@section Source and machine code
You can use the command @code{info line} to map source lines to program
--- 4166,4172 ----
directories in one command.
@end enumerate
! @node Machine Code
@section Source and machine code
You can use the command @code{info line} to map source lines to program
*************** assemblers for x86-based targets.
*** 4210,4216 ****
@end table
! @node Data, Languages, Source, Top
@chapter Examining Data
@cindex printing data
--- 4267,4273 ----
@end table
! @node Data
@chapter Examining Data
@cindex printing data
*************** Table}.
*** 4265,4271 ****
* Floating Point Hardware:: Floating point hardware
@end menu
! @node Expressions, Variables, Data, Data
@section Expressions
@cindex expressions
--- 4322,4328 ----
* Floating Point Hardware:: Floating point hardware
@end menu
! @node Expressions
@section Expressions
@cindex expressions
*************** a cast). This construct is allowed rega
*** 4318,4324 ****
normally supposed to reside at @var{addr}.
@end table
! @node Variables, Arrays, Expressions, Data
@section Program variables
The most common kind of expression to use is the name of a variable
--- 4375,4381 ----
normally supposed to reside at @var{addr}.
@end table
! @node Variables
@section Program variables
The most common kind of expression to use is the name of a variable
*************** Program or @sc{gnu} CC, gcc.info, Using
*** 4439,4445 ****
information.
! @node Arrays, Output Formats, Variables, Data
@section Artificial arrays
@cindex artificial array
--- 4496,4502 ----
information.
! @node Arrays
@section Artificial arrays
@cindex artificial array
*************** p dtab[$i++]->fv
*** 4511,4517 ****
@dots{}
@end example
! @node Output Formats, Memory, Arrays, Data
@section Output formats
@cindex formatted output
--- 4568,4574 ----
@dots{}
@end example
! @node Output Formats
@section Output formats
@cindex formatted output
*************** To reprint the last value in the value h
*** 4580,4586 ****
you can use the @code{print} command with just a format and no
expression. For example, @samp{p/x} reprints the last value in hex.
! @node Memory, Auto Display, Output Formats, Data
@section Examining memory
You can use the command @code{x} (for ``examine'') to examine memory in
--- 4637,4643 ----
you can use the @code{print} command with just a format and no
expression. For example, @samp{p/x} reprints the last value in hex.
! @node Memory
@section Examining memory
You can use the command @code{x} (for ``examine'') to examine memory in
*************** If the @code{x} command has a repeat cou
*** 4685,4691 ****
are from the last memory unit printed; this is not the same as the last
address printed if several units were printed on the last line of output.
! @node Auto Display, Print Settings, Memory, Data
@section Automatic display
@cindex automatic display
@cindex display of expressions
--- 4742,4748 ----
are from the last memory unit printed; this is not the same as the last
address printed if several units were printed on the last line of output.
! @node Auto Display
@section Automatic display
@cindex automatic display
@cindex display of expressions
*************** there is no variable @code{last_char}---
*** 4781,4787 ****
automatically. The next time your program stops where @code{last_char}
is meaningful, you can enable the display expression once again.
! @node Print Settings, Value History, Auto Display, Data
@section Print settings
@cindex format options
--- 4838,4844 ----
automatically. The next time your program stops where @code{last_char}
is meaningful, you can enable the display expression once again.
! @node Print Settings
@section Print settings
@cindex format options
*************** Do not pretty print C++ virtual function
*** 5142,5148 ****
Show whether C++ virtual function tables are pretty printed, or not.
@end table
! @node Value History, Convenience Vars, Print Settings, Data
@section Value history
@cindex value history
--- 5199,5205 ----
Show whether C++ virtual function tables are pretty printed, or not.
@end table
! @node Value History
@section Value history
@cindex value history
*************** values are available, @code{show values
*** 5219,5225 ****
Pressing @key{RET} to repeat @code{show values @var{n}} has exactly the
same effect as @samp{show values +}.
! @node Convenience Vars, Registers, Value History, Data
@section Convenience variables
@cindex convenience variables
--- 5276,5282 ----
Pressing @key{RET} to repeat @code{show values @var{n}} has exactly the
same effect as @samp{show values +}.
! @node Convenience Vars
@section Convenience variables
@cindex convenience variables
*************** On HP-UX systems, if you refer to a func
*** 5305,5311 ****
begins with a dollar sign, @value{GDBN} searches for a user or system
name first, before it searches for a convenience variable.
! @node Registers, Floating Point Hardware, Convenience Vars, Data
@section Registers
@cindex registers
--- 5362,5368 ----
begins with a dollar sign, @value{GDBN} searches for a user or system
name first, before it searches for a convenience variable.
! @node Registers
@section Registers
@cindex registers
*************** code generated by your compiler. If som
*** 5404,5410 ****
@value{GDBN} is unable to locate the saved registers, the selected stack
frame makes no difference.
! @node Floating Point Hardware, , Registers, Data
@section Floating point hardware
@cindex floating point
--- 5461,5467 ----
@value{GDBN} is unable to locate the saved registers, the selected stack
frame makes no difference.
! @node Floating Point Hardware
@section Floating point hardware
@cindex floating point
*************** floating point chip. Currently, @samp{i
*** 5420,5426 ****
the ARM and x86 machines.
@end table
! @node Languages, Symbols, Data, Top
@chapter Using @value{GDBN} with Different Languages
@cindex languages
--- 5477,5483 ----
the ARM and x86 machines.
@end table
! @node Languages
@chapter Using @value{GDBN} with Different Languages
@cindex languages
*************** language}.
*** 5446,5452 ****
* Support:: Supported languages
@end menu
! @node Setting, Show, Languages, Languages
@section Switching between source languages
There are two ways to control the working language---either have @value{GDBN}
--- 5503,5509 ----
* Support:: Supported languages
@end menu
! @node Setting
@section Switching between source languages
There are two ways to control the working language---either have @value{GDBN}
*************** program, and will display that source co
*** 5480,5486 ****
* Automatically:: Having @value{GDBN} infer the source language
@end menu
! @node Filenames, Manually, Setting, Setting
@subsection List of filename extensions and languages
If a source file name ends in one of the following extensions, then
--- 5537,5543 ----
* Automatically:: Having @value{GDBN} infer the source language
@end menu
! @node Filenames
@subsection List of filename extensions and languages
If a source file name ends in one of the following extensions, then
*************** Assembler source file. This actually be
*** 5520,5526 ****
In addition, you may set the language associated with a filename
extension. @xref{Show, , Displaying the language}.
! @node Manually, Automatically, Filenames, Setting
@subsection Setting the working language
If you allow @value{GDBN} to set the language automatically,
--- 5577,5583 ----
In addition, you may set the language associated with a filename
extension. @xref{Show, , Displaying the language}.
! @node Manually
@subsection Setting the working language
If you allow @value{GDBN} to set the language automatically,
*************** might not have the effect you intended.
*** 5552,5558 ****
printed would be the value of @code{a}. In Modula-2, this means to compare
@code{a} to the result of @code{b+c}, yielding a @code{BOOLEAN} value.
! @node Automatically, , Manually, Setting
@subsection Having @value{GDBN} infer the source language
To have @value{GDBN} set the working language automatically, use
--- 5609,5615 ----
printed would be the value of @code{a}. In Modula-2, this means to compare
@code{a} to the result of @code{b+c}, yielding a @code{BOOLEAN} value.
! @node Automatically
@subsection Having @value{GDBN} infer the source language
To have @value{GDBN} set the working language automatically, use
*************** written in one source language can be us
*** 5571,5577 ****
a different source language. Using @samp{set language auto} in this
case frees you from having to set the working language manually.
! @node Show, Checks, Setting, Languages
@section Displaying the language
The following commands help you find out which language is the
--- 5628,5634 ----
a different source language. Using @samp{set language auto} in this
case frees you from having to set the working language manually.
! @node Show
@section Displaying the language
The following commands help you find out which language is the
*************** the source language @var{language}.
*** 5613,5619 ****
List all the filename extensions and the associated languages.
@end table
! @node Checks, Support, Show, Languages
@section Type and range checking
@quotation
--- 5670,5676 ----
List all the filename extensions and the associated languages.
@end table
! @node Checks
@section Type and range checking
@quotation
*************** for the default settings of supported la
*** 5646,5652 ****
@cindex type checking
@cindex checks, type
! @node Type Checking, Range Checking, Checks, Checks
@subsection An overview of type checking
Some languages, such as Modula-2, are strongly typed, meaning that the
--- 5703,5709 ----
@cindex type checking
@cindex checks, type
! @node Type Checking
@subsection An overview of type checking
Some languages, such as Modula-2, are strongly typed, meaning that the
*************** is setting it automatically.
*** 5717,5723 ****
@cindex range checking
@cindex checks, range
! @node Range Checking, , Type Checking, Checks
@subsection An overview of range checking
In some languages (such as Modula-2), it is an error to exceed the
--- 5774,5780 ----
@cindex range checking
@cindex checks, range
! @node Range Checking
@subsection An overview of range checking
In some languages (such as Modula-2), it is an error to exceed the
*************** Show the current setting of the range ch
*** 5776,5782 ****
being set automatically by @value{GDBN}.
@end table
! @node Support, , Checks, Languages
@section Supported languages
@value{GDBN} supports C, C++, Fortran, Java, Chill, assembly, and Modula-2.
--- 5833,5839 ----
being set automatically by @value{GDBN}.
@end table
! @node Support
@section Supported languages
@value{GDBN} supports C, C++, Fortran, Java, Chill, assembly, and Modula-2.
*************** language reference or tutorial.
*** 5801,5807 ****
* Chill:: Chill
@end menu
! @node C, Modula-2, Support, Support
@subsection C and C++
@cindex C and C++
--- 5858,5864 ----
* Chill:: Chill
@end menu
! @node C
@subsection C and C++
@cindex C and C++
*************** CC, gcc.info, Using @sc{gnu} CC}, for mo
*** 5836,5842 ****
* Debugging C plus plus:: @value{GDBN} features for C++
@end menu
! @node C Operators, C Constants, C, C
@subsubsection C and C++ operators
@cindex C and C++ operators
--- 5893,5899 ----
* Debugging C plus plus:: @value{GDBN} features for C++
@end menu
! @node C Operators
@subsubsection C and C++ operators
@cindex C and C++ operators
*************** predefined meaning.
*** 5996,6002 ****
* C Constants::
@end menu
! @node C Constants, C plus plus expressions, C Operators, C
@subsubsection C and C++ constants
@cindex C and C++ constants
--- 6053,6059 ----
* C Constants::
@end menu
! @node C Constants
@subsubsection C and C++ constants
@cindex C and C++ constants
*************** and @samp{@{&"hi", &"there", &"fred"@}}
*** 6064,6070 ****
* Debugging C::
@end menu
! @node C plus plus expressions, C Defaults, C Constants, C
@subsubsection C++ expressions
@cindex expressions in C++
--- 6121,6127 ----
* Debugging C::
@end menu
! @node C plus plus expressions
@subsubsection C++ expressions
@cindex expressions in C++
*************** calling virtual functions correctly, pri
*** 6169,6175 ****
objects, calling functions in a base subobject, casting objects, and
invoking user-defined operators.
! @node C Defaults, C Checks, C plus plus expressions, C
@subsubsection C and C++ defaults
@cindex C and C++ defaults
--- 6226,6232 ----
objects, calling functions in a base subobject, casting objects, and
invoking user-defined operators.
! @node C Defaults
@subsubsection C and C++ defaults
@cindex C and C++ defaults
*************** for further details.
*** 6190,6196 ****
@c unimplemented. If (b) changes, it might make sense to let this node
@c appear even if Mod-2 does not, but meanwhile ignore it. roland 16jul93.
! @node C Checks, Debugging C, C Defaults, C
@subsubsection C and C++ type and range checks
@cindex C and C++ checks
--- 6247,6253 ----
@c unimplemented. If (b) changes, it might make sense to let this node
@c appear even if Mod-2 does not, but meanwhile ignore it. roland 16jul93.
! @node C Checks
@subsubsection C and C++ type and range checks
@cindex C and C++ checks
*************** Range checking, if turned on, is done on
*** 6222,6228 ****
indices are not checked, since they are often used to index a pointer
that is not itself an array.
! @node Debugging C, Debugging C plus plus, C Checks, C
@subsubsection @value{GDBN} and C
The @code{set print union} and @code{show print union} commands apply to
--- 6279,6285 ----
indices are not checked, since they are often used to index a pointer
that is not itself an array.
! @node Debugging C
@subsubsection @value{GDBN} and C
The @code{set print union} and @code{show print union} commands apply to
*************** with pointers and a memory allocation fu
*** 6238,6244 ****
* Debugging C plus plus::
@end menu
! @node Debugging C plus plus, , Debugging C, C
@subsubsection @value{GDBN} features for C++
@cindex commands for C++
--- 6295,6301 ----
* Debugging C plus plus::
@end menu
! @node Debugging C plus plus
@subsubsection @value{GDBN} features for C++
@cindex commands for C++
*************** available choices, or to finish the type
*** 6321,6327 ****
@xref{Completion,, Command completion}, for details on how to do this.
@end table
! @node Modula-2, Chill, C, Support
@subsection Modula-2
@cindex Modula-2, @value{GDBN} support
--- 6378,6384 ----
@xref{Completion,, Command completion}, for details on how to do this.
@end table
! @node Modula-2
@subsection Modula-2
@cindex Modula-2, @value{GDBN} support
*************** table.
*** 6345,6351 ****
* GDB/M2:: @value{GDBN} and Modula-2
@end menu
! @node M2 Operators, Built-In Func/Proc, Modula-2, Modula-2
@subsubsection Operators
@cindex Modula-2 operators
--- 6402,6408 ----
* GDB/M2:: @value{GDBN} and Modula-2
@end menu
! @node M2 Operators
@subsubsection Operators
@cindex Modula-2 operators
*************** treats the use of the operator @code{IN}
*** 6469,6475 ****
@end quotation
@cindex Modula-2 built-ins
! @node Built-In Func/Proc, M2 Constants, M2 Operators, Modula-2
@subsubsection Built-in functions and procedures
Modula-2 also makes available several built-in procedures and functions.
--- 6526,6532 ----
@end quotation
@cindex Modula-2 built-ins
! @node Built-In Func/Proc
@subsubsection Built-in functions and procedures
Modula-2 also makes available several built-in procedures and functions.
*************** an error.
*** 6581,6587 ****
@end quotation
@cindex Modula-2 constants
! @node M2 Constants, M2 Defaults, Built-In Func/Proc, Modula-2
@subsubsection Constants
@value{GDBN} allows you to express the constants of Modula-2 in the following
--- 6638,6644 ----
@end quotation
@cindex Modula-2 constants
! @node M2 Constants
@subsubsection Constants
@value{GDBN} allows you to express the constants of Modula-2 in the following
*************** Pointer constants consist of integral va
*** 6630,6636 ****
Set constants are not yet supported.
@end itemize
! @node M2 Defaults, Deviations, M2 Constants, Modula-2
@subsubsection Modula-2 defaults
@cindex Modula-2 defaults
--- 6687,6693 ----
Set constants are not yet supported.
@end itemize
! @node M2 Defaults
@subsubsection Modula-2 defaults
@cindex Modula-2 defaults
*************** code compiled from a file whose name end
*** 6644,6650 ****
working language to Modula-2. @xref{Automatically, ,Having @value{GDBN} set
the language automatically}, for further details.
! @node Deviations, M2 Checks, M2 Defaults, Modula-2
@subsubsection Deviations from standard Modula-2
@cindex Modula-2, deviations from
--- 6701,6707 ----
working language to Modula-2. @xref{Automatically, ,Having @value{GDBN} set
the language automatically}, for further details.
! @node Deviations
@subsubsection Deviations from standard Modula-2
@cindex Modula-2, deviations from
*************** argument.
*** 6674,6680 ****
All built-in procedures both modify @emph{and} return their argument.
@end itemize
! @node M2 Checks, M2 Scope, Deviations, Modula-2
@subsubsection Modula-2 type and range checks
@cindex Modula-2 checks
--- 6731,6737 ----
All built-in procedures both modify @emph{and} return their argument.
@end itemize
! @node M2 Checks
@subsubsection Modula-2 type and range checks
@cindex Modula-2 checks
*************** whose types are not equivalent is an err
*** 6702,6708 ****
Range checking is done on all mathematical operations, assignment, array
index bounds, and all built-in functions and procedures.
! @node M2 Scope, GDB/M2, M2 Checks, Modula-2
@subsubsection The scope operators @code{::} and @code{.}
@cindex scope
@kindex .
--- 6759,6765 ----
Range checking is done on all mathematical operations, assignment, array
index bounds, and all built-in functions and procedures.
! @node M2 Scope
@subsubsection The scope operators @code{::} and @code{.}
@cindex scope
@kindex .
*************** an error if the identifier @var{id} was
*** 6742,6748 ****
module @var{module}, or if @var{id} is not an identifier in
@var{module}.
! @node GDB/M2, , M2 Scope, Modula-2
@subsubsection @value{GDBN} and Modula-2
Some @value{GDBN} commands have little use when debugging Modula-2 programs.
--- 6799,6805 ----
module @var{module}, or if @var{id} is not an identifier in
@var{module}.
! @node GDB/M2
@subsubsection @value{GDBN} and Modula-2
Some @value{GDBN} commands have little use when debugging Modula-2 programs.
*************** address can be specified by an integral
*** 6763,6769 ****
In @value{GDBN} scripts, the Modula-2 inequality operator @code{#} is
interpreted as the beginning of a comment. Use @code{<>} instead.
! @node Chill, , Modula-2, Support
@subsection Chill
The extensions made to @value{GDBN} to support Chill only support output
--- 6820,6826 ----
In @value{GDBN} scripts, the Modula-2 inequality operator @code{#} is
interpreted as the beginning of a comment. Use @code{<>} instead.
! @node Chill
@subsection Chill
The extensions made to @value{GDBN} to support Chill only support output
*************** of @value{GDBN} which support these topi
*** 6785,6791 ****
* Chill defaults::
@end menu
! @node How modes are displayed, Locations, Chill, Chill
@subsubsection How modes are displayed
The Chill Datatype- (Mode) support of @value{GDBN} is directly related
--- 6842,6848 ----
* Chill defaults::
@end menu
! @node How modes are displayed
@subsubsection How modes are displayed
The Chill Datatype- (Mode) support of @value{GDBN} is directly related
*************** type = SET (karli = 10, susi = 20, fritz
*** 6813,6822 ****
@end smallexample
If the type is an unnumbered set the set element values are omitted.
@item
! @emph{Range Mode} which is displayed by @code{type = <basemode>
! (<lower bound> : <upper bound>)}, where @code{<lower bound>, <upper
! bound>} can be of any discrete literal expression (e.g. set element
! names).
@end itemize
@item @r{@emph{Powerset Mode:}}
--- 6870,6881 ----
@end smallexample
If the type is an unnumbered set the set element values are omitted.
@item
! @emph{Range Mode} which is displayed by
! @smallexample
! @code{type = <basemode>(<lower bound> : <upper bound>)}
! @end smallexample
! where @code{<lower bound>, <upper bound>} can be of any discrete literal
! expression (e.g. set element names).
@end itemize
@item @r{@emph{Powerset Mode:}}
*************** type, and is therefore not really of int
*** 6852,6862 ****
@item @r{@emph{Synchronization Modes:}}
@itemize @bullet
@item
! @emph{Event Mode} which is displayed by @code{EVENT (<event length>)},
where @code{(<event length>)} is optional.
@item
! @emph{Buffer Mode} which is displayed by @code{BUFFER (<buffer length>)
! <buffer element mode>}, where @code{(<buffer length>)} is optional.
@end itemize
@item @r{@emph{Timing Modes:}}
--- 6911,6927 ----
@item @r{@emph{Synchronization Modes:}}
@itemize @bullet
@item
! @emph{Event Mode} which is displayed by
! @smallexample
! @code{EVENT (<event length>)}
! @end smallexample
where @code{(<event length>)} is optional.
@item
! @emph{Buffer Mode} which is displayed by
! @smallexample
! @code{BUFFER (<buffer length>)<buffer element mode>}
! @end smallexample
! where @code{(<buffer length>)} is optional.
@end itemize
@item @r{@emph{Timing Modes:}}
*************** Real Modes are predefined with @code{REA
*** 6873,6884 ****
@item @r{@emph{String Modes:}}
@itemize @bullet
@item
! @emph{Character String Mode} which is displayed by @code{CHARS(<string
! length>)}, followed by the keyword @code{VARYING} if the String Mode is
! a varying mode
@item
! @emph{Bit String Mode} which is displayed by @code{BOOLS(<string
! length>)}.
@end itemize
@item @r{@emph{Array Mode:}}
--- 6938,6955 ----
@item @r{@emph{String Modes:}}
@itemize @bullet
@item
! @emph{Character String Mode} which is displayed by
! @smallexample
! @code{CHARS(<string length>)}
! @end smallexample
! followed by the keyword @code{VARYING} if the String Mode is a varying
! mode
@item
! @emph{Bit String Mode} which is displayed by
! @smallexample
! @code{BOOLS(<string
! length>)}
! @end smallexample
@end itemize
@item @r{@emph{Array Mode:}}
*************** type = STRUCT (
*** 6914,6920 ****
@end smallexample
@end table
! @node Locations, Values and their Operations, How modes are displayed, Chill
@subsubsection Locations and their accesses
A location in Chill is an object which can contain values.
--- 6985,6991 ----
@end smallexample
@end table
! @node Locations
@subsubsection Locations and their accesses
A location in Chill is an object which can contain values.
*************** represents the address where the referen
*** 6942,6952 ****
value of the location referenced by the pointer, use the dereference
operator @samp{->}.
! Values of procedure mode locations are displayed by @code{@{ PROC
(<argument modes> ) <return mode> @} <address> <name of procedure
! location>}. @code{<argument modes>} is a list of modes according to the
! parameter specification of the procedure and @code{<address>} shows the
! address of the entry point.
@ignore
Locations of instance modes are displayed just like a structure with two
--- 7013,7027 ----
value of the location referenced by the pointer, use the dereference
operator @samp{->}.
! Values of procedure mode locations are displayed by
! @smallexample
! @code{@{ PROC
(<argument modes> ) <return mode> @} <address> <name of procedure
! location>}
! @end smallexample
! @code{<argument modes>} is a list of modes according to the parameter
! specification of the procedure and @code{<address>} shows the address of
! the entry point.
@ignore
Locations of instance modes are displayed just like a structure with two
*************** therefore the result can be quite confus
*** 6995,7001 ****
(@value{GDBP}) print int (s(3 up 4)) XXX TO be filled in !! XXX
@end smallexample
! @node Values and their Operations, Chill type and range checks, Locations, Chill
@subsubsection Values and their Operations
Values are used to alter locations, to investigate complex structures in
--- 7070,7076 ----
(@value{GDBP}) print int (s(3 up 4)) XXX TO be filled in !! XXX
@end smallexample
! @node Values and their Operations
@subsubsection Values and their Operations
Values are used to alter locations, to investigate complex structures in
*************** same manner as in Chill programs refer t
*** 7065,7071 ****
@end itemize
@item String Element Value
! A string element value is specified by @code{<string value>(<index>)},
where @code{<index>} is a integer expression. It delivers a character
value which is equivalent to the character indexed by @code{<index>} in
the string.
--- 7140,7149 ----
@end itemize
@item String Element Value
! A string element value is specified by
! @smallexample
! @code{<string value>(<index>)}
! @end smallexample
where @code{<index>} is a integer expression. It delivers a character
value which is equivalent to the character indexed by @code{<index>} in
the string.
*************** expression, then this procedure is calle
*** 7102,7109 ****
effects. This can lead to confusing results if used carelessly.}.
Values of duration mode locations are represented by @code{ULONG} literals.
- Values of time mode locations are represented by @code{TIME(<secs>:<nsecs>)}.
@ignore
This is not implemented yet:
--- 7180,7191 ----
effects. This can lead to confusing results if used carelessly.}.
Values of duration mode locations are represented by @code{ULONG} literals.
+
+ Values of time mode locations appear as
+ @smallexample
+ @code{TIME(<secs>:<nsecs>)}
+ @end smallexample
@ignore
This is not implemented yet:
*************** Membership operator.
*** 7198,7204 ****
@end table
@end table
! @node Chill type and range checks, Chill defaults, Values and their Operations, Chill
@subsubsection Chill type and range checks
@value{GDBN} considers two Chill variables mode equivalent if the sizes
--- 7280,7286 ----
@end table
@end table
! @node Chill type and range checks
@subsubsection Chill type and range checks
@value{GDBN} considers two Chill variables mode equivalent if the sizes
*************** off}.
*** 7224,7230 ****
see last paragraph ?
@end ignore
! @node Chill defaults, , Chill type and range checks, Chill
@subsubsection Chill defaults
If type and range checking are set automatically by @value{GDBN}, they
--- 7306,7312 ----
see last paragraph ?
@end ignore
! @node Chill defaults
@subsubsection Chill defaults
If type and range checking are set automatically by @value{GDBN}, they
*************** code compiled from a file whose name end
*** 7237,7243 ****
working language to Chill. @xref{Automatically, ,Having @value{GDBN} set
the language automatically}, for further details.
! @node Symbols, Altering, Languages, Top
@chapter Examining the Symbol Table
The commands described in this chapter allow you to inquire about the
--- 7319,7325 ----
working language to Chill. @xref{Automatically, ,Having @value{GDBN} set
the language automatically}, for further details.
! @node Symbols
@chapter Examining the Symbol Table
The commands described in this chapter allow you to inquire about the
*************** Replace symbol definitions for the corre
*** 7402,7413 ****
object file with a particular name is seen again.
@item set symbol-reloading off
! Do not replace symbol definitions when re-encountering object files of
! the same name. This is the default state; if you are not running on a
! system that permits automatically relinking modules, you should leave
! @code{symbol-reloading} off, since otherwise @value{GDBN} may discard symbols
! when linking large programs, that may contain several modules (from
! different directories or libraries) with the same name.
@kindex show symbol-reloading
@item show symbol-reloading
--- 7484,7496 ----
object file with a particular name is seen again.
@item set symbol-reloading off
! Do not replace symbol definitions when encountering object files of the
! same name more than once. This is the default state; if you are not
! running on a system that permits automatic relinking of modules, you
! should leave @code{symbol-reloading} off, since otherwise @value{GDBN}
! may discard symbols when linking large programs, that may contain
! several modules (from different directories or libraries) with the same
! name.
@kindex show symbol-reloading
@item show symbol-reloading
*************** required for each object file from which
*** 7459,7465 ****
@value{GDBN} reads symbols (in the description of @code{symbol-file}).
@end table
! @node Altering, GDB Files, Symbols, Top
@chapter Altering Execution
Once you think you have found an error in your program, you might want to
--- 7542,7548 ----
@value{GDBN} reads symbols (in the description of @code{symbol-file}).
@end table
! @node Altering
@chapter Altering Execution
Once you think you have found an error in your program, you might want to
*************** address, or even return prematurely from
*** 7481,7487 ****
* Patching:: Patching your program
@end menu
! @node Assignment, Jumping, Altering, Altering
@section Assignment to variables
@cindex assignment
--- 7564,7570 ----
* Patching:: Patching your program
@end menu
! @node Assignment
@section Assignment to variables
@cindex assignment
*************** $2 = 1
*** 7552,7558 ****
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/smith/cc_progs/a.out
! "/home/smith/cc_progs/a.out": can't open to read symbols: Invalid bfd target.
(@value{GDBP}) show g
The current BFD target is "=4".
@end group
--- 7635,7642 ----
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/smith/cc_progs/a.out
! "/home/smith/cc_progs/a.out": can't open to read symbols:
! Invalid bfd target.
(@value{GDBP}) show g
The current BFD target is "=4".
@end group
*************** set @{int@}0x83040 = 4
*** 7587,7593 ****
@noindent
stores the value 4 into that memory location.
! @node Jumping, Signaling, Assignment, Altering
@section Continuing at a different address
Ordinarily, when you continue your program, you do so at the place where
--- 7671,7677 ----
@noindent
stores the value 4 into that memory location.
! @node Jumping
@section Continuing at a different address
Ordinarily, when you continue your program, you do so at the place where
*************** that has already executed, in order to e
*** 7640,7646 ****
detail.
@c @group
! @node Signaling, Returning, Jumping, Altering
@section Giving your program a signal
@table @code
--- 7724,7730 ----
detail.
@c @group
! @node Signaling
@section Giving your program a signal
@table @code
*************** the signal handling tables (@pxref{Signa
*** 7669,7675 ****
passes the signal directly to your program.
! @node Returning, Calling, Signaling, Altering
@section Returning from a function
@table @code
--- 7753,7759 ----
passes the signal directly to your program.
! @node Returning
@section Returning from a function
@table @code
*************** returned. In contrast, the @code{finish
*** 7700,7706 ****
and Stepping, ,Continuing and stepping}) resumes execution until the
selected stack frame returns naturally.
! @node Calling, Patching, Returning, Altering
@section Calling program functions
@cindex calling functions
--- 7784,7790 ----
and Stepping, ,Continuing and stepping}) resumes execution until the
selected stack frame returns naturally.
! @node Calling
@section Calling program functions
@cindex calling functions
*************** calls a function in the target. This is
*** 7722,7728 ****
method of putting the scratch area on the stack does not work in systems
that have separate instruction and data spaces.
! @node Patching, , Calling, Altering
@section Patching programs
@cindex patching binaries
--- 7806,7812 ----
method of putting the scratch area on the stack does not work in systems
that have separate instruction and data spaces.
! @node Patching
@section Patching programs
@cindex patching binaries
*************** Display whether executable files and cor
*** 7757,7763 ****
as well as reading.
@end table
! @node GDB Files, Targets, Altering, Top
@chapter @value{GDBN} Files
@value{GDBN} needs to know the file name of the program to be debugged,
--- 7841,7847 ----
as well as reading.
@end table
! @node GDB Files
@chapter @value{GDBN} Files
@value{GDBN} needs to know the file name of the program to be debugged,
*************** program. To debug a core dump of a prev
*** 7770,7776 ****
* Symbol Errors:: Errors reading symbol files
@end menu
! @node Files, Symbol Errors, GDB Files, GDB Files
@section Commands to specify files
@cindex symbol table
--- 7854,7860 ----
* Symbol Errors:: Errors reading symbol files
@end menu
! @node Files
@section Commands to specify files
@cindex symbol table
*************** directories to search, just as the shell
*** 7799,7805 ****
to run. You can change the value of this variable, for both @value{GDBN}
and your program, using the @code{path} command.
! On systems with memory-mapped files, an auxiliary file
@file{@var{filename}.syms} may hold symbol table information for
@var{filename}. If so, @value{GDBN} maps in the symbol table from
@file{@var{filename}.syms}, starting up more quickly. See the
--- 7883,7889 ----
to run. You can change the value of this variable, for both @value{GDBN}
and your program, using the @code{path} command.
! On systems with memory-mapped files, an auxiliary file named
@file{@var{filename}.syms} may hold symbol table information for
@var{filename}. If so, @value{GDBN} maps in the symbol table from
@file{@var{filename}.syms}, starting up more quickly. See the
*************** Otherwise, symbols must be loaded manual
*** 8050,8056 ****
Display the current autoloading size threshold, in megabytes.
@end table
! @node Symbol Errors, , Files, GDB Files
@section Errors reading symbol files
While reading a symbol file, @value{GDBN} occasionally encounters problems,
--- 8134,8140 ----
Display the current autoloading size threshold, in megabytes.
@end table
! @node Symbol Errors
@section Errors reading symbol files
While reading a symbol file, @value{GDBN} occasionally encounters problems,
*************** it.
*** 8139,8145 ****
@end table
! @node Targets, Configurations, GDB Files, Top
@chapter Specifying a Debugging Target
@cindex debugging target
--- 8223,8229 ----
@end table
! @node Targets
@chapter Specifying a Debugging Target
@cindex debugging target
*************** command to specify one of the target typ
*** 8165,8171 ****
@end menu
! @node Active Targets, Target Commands, Targets, Targets
@section Active targets
@cindex stacking targets
--- 8249,8255 ----
@end menu
! @node Active Targets
@section Active targets
@cindex stacking targets
*************** files}). To specify as a target a proce
*** 8200,8206 ****
the @code{attach} command (@pxref{Attach, ,Debugging an already-running
process}).
! @node Target Commands, Byte Order, Active Targets, Targets
@section Commands for managing targets
@table @code
--- 8284,8290 ----
the @code{attach} command (@pxref{Attach, ,Debugging an already-running
process}).
! @node Target Commands
@section Commands for managing targets
@table @code
*************** specifies a fixed address.
*** 8332,8338 ****
@code{load} does not repeat if you press @key{RET} again after using it.
@end table
! @node Byte Order, Remote, Target Commands, Targets
@section Choosing target byte order
@cindex choosing target byte order
--- 8416,8422 ----
@code{load} does not repeat if you press @key{RET} again after using it.
@end table
! @node Byte Order
@section Choosing target byte order
@cindex choosing target byte order
*************** Note that these commands merely adjust i
*** 8372,8378 ****
data on the host, and that they have absolutely no effect on the
target system.
! @node Remote, KOD, Byte Order, Targets
@section Remote debugging
@cindex remote debugging
--- 8456,8462 ----
data on the host, and that they have absolutely no effect on the
target system.
! @node Remote
@section Remote debugging
@cindex remote debugging
*************** configuration of @value{GDBN}; use @code
*** 8396,8402 ****
* Remote Serial:: @value{GDBN} remote serial protocol
@end menu
! @node Remote Serial, , Remote, Remote
@subsection The @value{GDBN} remote serial protocol
@cindex remote serial debugging, overview
--- 8480,8486 ----
* Remote Serial:: @value{GDBN} remote serial protocol
@end menu
! @node Remote Serial
@subsection The @value{GDBN} remote serial protocol
@cindex remote serial debugging, overview
*************** recently added stubs.
*** 8494,8500 ****
* NetWare:: Using the `gdbserve.nlm' program
@end menu
! @node Stub Contents, Bootstrapping, Remote Serial, Remote Serial
@subsubsection What the stub can do for you
@cindex remote serial stub
--- 8578,8584 ----
* NetWare:: Using the `gdbserve.nlm' program
@end menu
! @node Stub Contents
@subsubsection What the stub can do for you
@cindex remote serial stub
*************** to make certain your program stops at a
*** 8545,8551 ****
start of your debugging session.
@end table
! @node Bootstrapping, Debug Session, Stub Contents, Remote Serial
@subsubsection What you must do for the stub
@cindex remote stub, support routines
--- 8629,8635 ----
start of your debugging session.
@end table
! @node Bootstrapping
@subsubsection What you must do for the stub
@cindex remote stub, support routines
*************** but in general the stubs are likely to u
*** 8636,8642 ****
subroutines which @code{@value{GCC}} generates as inline code.
! @node Debug Session, Protocol, Bootstrapping, Remote Serial
@subsubsection Putting it all together
@cindex remote serial debugging summary
--- 8720,8726 ----
subroutines which @code{@value{GCC}} generates as inline code.
! @node Debug Session
@subsubsection Putting it all together
@cindex remote serial debugging summary
*************** steps.
*** 8645,8651 ****
@enumerate
@item
! Make sure you have the supporting low-level routines
(@pxref{Bootstrapping,,What you must do for the stub}):
@display
@code{getDebugChar}, @code{putDebugChar},
--- 8729,8735 ----
@enumerate
@item
! Make sure you have defined the supporting low-level routines
(@pxref{Bootstrapping,,What you must do for the stub}):
@display
@code{getDebugChar}, @code{putDebugChar},
*************** If you type @kbd{y}, @value{GDBN} abando
*** 8742,8748 ****
remote} again to connect once more.) If you type @kbd{n}, @value{GDBN}
goes back to waiting.
! @node Protocol, Server, Debug Session, Remote Serial
@subsubsection Communication protocol
@cindex debugging stub, example
--- 8826,8832 ----
remote} again to connect once more.) If you type @kbd{n}, @value{GDBN}
goes back to waiting.
! @node Protocol
@subsubsection Communication protocol
@cindex debugging stub, example
*************** bytes. For a software breakpoint, @var{
*** 9264,9270 ****
the instruction to be patched. For hardware breakpoints and watchpoints
@var{length} specifies the memory region to be monitored. To avoid
potential problems with duplicate packets, the operations should be
! implemented in an ident-potentent way.
@item
@tab reply @code{E}@var{NN}
@tab for an error
--- 9348,9354 ----
the instruction to be patched. For hardware breakpoints and watchpoints
@var{length} specifies the memory region to be monitored. To avoid
potential problems with duplicate packets, the operations should be
! implemented in an idempotent way.
@item
@tab reply @code{E}@var{NN}
@tab for an error
*************** applicable for certains sorts of targets
*** 9312,9325 ****
@tab
The process terminated with signal @var{AA}.
! @item @code{N}@var{AA}@code{;}@var{tttttttt}@code{;}@var{dddddddd}@code{;}@var{bbbbbbbb} @strong{(obsolete)}
@tab
! @var{AA} = signal number; @var{tttttttt} = address of symbol "_start";
! @var{dddddddd} = base of data section; @var{bbbbbbbb} = base of bss
! section. @emph{Note: only used by Cisco Systems targets. The difference
! between this reply and the "qOffsets" query is that the 'N' packet may
! arrive spontaneously whereas the 'qOffsets' is a query initiated by the
! host debugger.}
@item @code{O}@var{XX...}
@tab
--- 9396,9409 ----
@tab
The process terminated with signal @var{AA}.
! @item @code{N}@var{AA}@code{;}@var{t...}@code{;}@var{d...}@code{;}@var{b...} @strong{(obsolete)}
@tab
! @var{AA} = signal number; @var{t...} = address of symbol "_start";
! @var{d...} = base of data section; @var{b...} = base of bss section.
! @emph{Note: only used by Cisco Systems targets. The difference between
! this reply and the "qOffsets" query is that the 'N' packet may arrive
! spontaneously whereas the 'qOffsets' is a query initiated by the host
! debugger.}
@item @code{O}@var{XX...}
@tab
*************** Example sequence of a target being stepp
*** 9536,9542 ****
<- @code{+}
@end example
! @node Server, NetWare, Protocol, Remote Serial
@subsubsection Using the @code{gdbserver} program
@kindex gdbserver
--- 9620,9626 ----
<- @code{+}
@end example
! @node Server
@subsubsection Using the @code{gdbserver} program
@kindex gdbserver
*************** text depends on the host system, but whi
*** 9638,9644 ****
@samp{Connection refused}.
@end table
! @node NetWare, , Server, Remote Serial
@subsubsection Using the @code{gdbserve.nlm} program
@kindex gdbserve.nlm
--- 9722,9728 ----
@samp{Connection refused}.
@end table
! @node NetWare
@subsubsection Using the @code{gdbserve.nlm} program
@kindex gdbserve.nlm
*************** argument is a device name (usually a ser
*** 9695,9701 ****
communications with the server via serial line @file{/dev/ttyb}.
@end table
! @node KOD, , Remote, Targets
@section Kernel Object Display
@cindex kernel object display
--- 9779,9785 ----
communications with the server via serial line @file{/dev/ttyb}.
@end table
! @node KOD
@section Kernel Object Display
@cindex kernel object display
*************** There is currently no way to determine w
*** 9734,9740 ****
is supported other than to try it.
! @node Configurations, Controlling GDB, Targets, Top
@chapter Configuration-Specific Information
While nearly all @value{GDBN} commands are available for all native and
--- 9818,9824 ----
is supported other than to try it.
! @node Configurations
@chapter Configuration-Specific Information
While nearly all @value{GDBN} commands are available for all native and
*************** are quite different from each other.
*** 9754,9760 ****
* Architectures::
@end menu
! @node Native, Embedded OS, Configurations, Configurations
@section Native
This section describes details specific to particular native
--- 9838,9844 ----
* Architectures::
@end menu
! @node Native
@section Native
This section describes details specific to particular native
*************** configurations.
*** 9765,9778 ****
* SVR4 Process Information:: SVR4 process information
@end menu
! @node HP-UX, SVR4 Process Information, Native, Native
@subsection HP-UX
On HP-UX systems, if you refer to a function or variable name that
begins with a dollar sign, @value{GDBN} searches for a user or system
name first, before it searches for a convenience variable.
! @node SVR4 Process Information, , HP-UX, Native
@subsection SVR4 process information
@kindex /proc
--- 9849,9862 ----
* SVR4 Process Information:: SVR4 process information
@end menu
! @node HP-UX
@subsection HP-UX
On HP-UX systems, if you refer to a function or variable name that
begins with a dollar sign, @value{GDBN} searches for a user or system
name first, before it searches for a convenience variable.
! @node SVR4 Process Information
@subsection SVR4 process information
@kindex /proc
*************** received.
*** 9817,9823 ****
Show all the above information about the process.
@end table
! @node Embedded OS, Embedded Processors, Native, Configurations
@section Embedded Operating Systems
This section describes configurations involving the debugging of
--- 9901,9907 ----
Show all the above information about the process.
@end table
! @node Embedded OS
@section Embedded Operating Systems
This section describes configurations involving the debugging of
*************** architectures.
*** 9831,9837 ****
@value{GDBN} includes the ability to debug programs running on
various real-time operating systems.
! @node VxWorks, , Embedded OS, Embedded OS
@subsection Using @value{GDBN} with VxWorks
@cindex VxWorks
--- 9915,9921 ----
@value{GDBN} includes the ability to debug programs running on
various real-time operating systems.
! @node VxWorks
@subsection Using @value{GDBN} with VxWorks
@cindex VxWorks
*************** run @value{GDBN}. From your Unix host,
*** 9898,9904 ****
* VxWorks Attach:: Running tasks
@end menu
! @node VxWorks Connection, VxWorks Download, VxWorks, VxWorks
@subsubsection Connecting to VxWorks
The @value{GDBN} command @code{target} lets you connect to a VxWorks target on the
--- 9982,9988 ----
* VxWorks Attach:: Running tasks
@end menu
! @node VxWorks Connection
@subsubsection Connecting to VxWorks
The @value{GDBN} command @code{target} lets you connect to a VxWorks target on the
*************** When this happens, add the appropriate d
*** 9931,9937 ****
the @value{GDBN} command @code{path}, and execute the @code{target}
command again.
! @node VxWorks Download, VxWorks Attach, VxWorks Connection, VxWorks
@subsubsection VxWorks download
@cindex download to VxWorks
--- 10015,10021 ----
the @value{GDBN} command @code{path}, and execute the @code{target}
command again.
! @node VxWorks Download
@subsubsection VxWorks download
@cindex download to VxWorks
*************** history. (This is necessary in order to
*** 9977,9983 ****
debugger's data structures that reference the target system's symbol
table.)
! @node VxWorks Attach, , VxWorks Download, VxWorks
@subsubsection Running tasks
@cindex running VxWorks tasks
--- 10061,10067 ----
debugger's data structures that reference the target system's symbol
table.)
! @node VxWorks Attach
@subsubsection Running tasks
@cindex running VxWorks tasks
*************** where @var{task} is the VxWorks hexadeci
*** 9993,9999 ****
or suspended when you attach to it. Running tasks are suspended at
the time of attachment.
! @node Embedded Processors, Architectures, Embedded OS, Configurations
@section Embedded Processors
This section goes into details specific to particular embedded
--- 10077,10083 ----
or suspended when you attach to it. Running tasks are suspended at
the time of attachment.
! @node Embedded Processors
@section Embedded Processors
This section goes into details specific to particular embedded
*************** configurations.
*** 10018,10024 ****
* Z8000:: Zilog Z8000
@end menu
! @node A29K Embedded, ARM, Embedded Processors, Embedded Processors
@subsection AMD A29K Embedded
@menu
--- 10102,10108 ----
* Z8000:: Zilog Z8000
@end menu
! @node A29K Embedded
@subsection AMD A29K Embedded
@menu
*************** name of the program to be debugged, as i
*** 10046,10052 ****
@end table
! @node A29K UDI, A29K EB29K, A29K Embedded, A29K Embedded
@subsubsection A29K UDI
@cindex UDI
--- 10130,10136 ----
@end table
! @node A29K UDI
@subsubsection A29K UDI
@cindex UDI
*************** working directory, you must set the envi
*** 10070,10076 ****
to its pathname.
@end table
! @node A29K EB29K, Comms (EB29K), A29K UDI, A29K Embedded
@subsubsection EBMON protocol for AMD29K
@cindex EB29K board
--- 10154,10160 ----
to its pathname.
@end table
! @node A29K EB29K
@subsubsection EBMON protocol for AMD29K
@cindex EB29K board
*************** board) and a serial port on the Unix sys
*** 10085,10091 ****
assume you've hooked the cable between the PC's @file{COM1} port and
@file{/dev/ttya} on the Unix system.
! @node Comms (EB29K), gdb-EB29K, A29K EB29K, A29K Embedded
@subsubsection Communications setup
The next step is to set up the PC's port, by doing something like this
--- 10169,10175 ----
assume you've hooked the cable between the PC's @file{COM1} port and
@file{/dev/ttya} on the Unix system.
! @node Comms (EB29K)
@subsubsection Communications setup
The next step is to set up the PC's port, by doing something like this
*************** other way---perhaps floppy-disk transfer
*** 10207,10213 ****
from the Unix system to the PC; @value{GDBN} does @emph{not} download it over the
serial line.
! @node gdb-EB29K, Remote Log, Comms (EB29K), A29K Embedded
@subsubsection EB29K cross-debugging
Finally, @code{cd} to the directory containing an image of your 29K
--- 10291,10297 ----
from the Unix system to the PC; @value{GDBN} does @emph{not} download it over the
serial line.
! @node gdb-EB29K
@subsubsection EB29K cross-debugging
Finally, @code{cd} to the directory containing an image of your 29K
*************** once again, after your @value{GDBN} sess
*** 10251,10257 ****
Type @kbd{CTTY con} to return command input to the main DOS console,
and type @kbd{~.} to leave @code{tip} or @code{cu}.
! @node Remote Log, , gdb-EB29K, A29K Embedded
@subsubsection Remote log
@kindex eb.log
@cindex log file for EB29K
--- 10335,10341 ----
Type @kbd{CTTY con} to return command input to the main DOS console,
and type @kbd{~.} to leave @code{tip} or @code{cu}.
! @node Remote Log
@subsubsection Remote log
@kindex eb.log
@cindex log file for EB29K
*************** of the commands sent to it. Running @sa
*** 10263,10269 ****
another window often helps to understand trouble with @code{EBMON}, or
unexpected events on the PC side of the connection.
! @node ARM, H8/300, A29K Embedded, Embedded Processors
@subsection ARM
@table @code
--- 10347,10353 ----
another window often helps to understand trouble with @code{EBMON}, or
unexpected events on the PC side of the connection.
! @node ARM
@subsection ARM
@table @code
*************** ARM Demon monitor.
*** 10280,10286 ****
@end table
! @node H8/300, H8/500, ARM, Embedded Processors
@subsection Hitachi H8/300
@table @code
--- 10364,10370 ----
@end table
! @node H8/300
@subsection Hitachi H8/300
@table @code
*************** what speed to use over the serial device
*** 10337,10343 ****
* Hitachi Special:: Special @value{GDBN} commands for Hitachi micros.
@end menu
! @node Hitachi Boards, Hitachi ICE, H8/300, H8/300
@subsubsection Connecting to Hitachi boards
@c only for Unix hosts
--- 10421,10427 ----
* Hitachi Special:: Special @value{GDBN} commands for Hitachi micros.
@end menu
! @node Hitachi Boards
@subsubsection Connecting to Hitachi boards
@c only for Unix hosts
*************** to detect program completion.
*** 10450,10456 ****
In either case, @value{GDBN} sees the effect of a @sc{reset} on the
development board as a ``normal exit'' of your program.
! @node Hitachi ICE, Hitachi Special, Hitachi Boards, H8/300
@subsubsection Using the E7000 in-circuit emulator
@kindex target e7000@r{, with Hitachi ICE}
--- 10534,10540 ----
In either case, @value{GDBN} sees the effect of a @sc{reset} on the
development board as a ``normal exit'' of your program.
! @node Hitachi ICE
@subsubsection Using the E7000 in-circuit emulator
@kindex target e7000@r{, with Hitachi ICE}
*************** If your E7000 is installed as a host on
*** 10470,10476 ****
specify its hostname; @value{GDBN} uses @code{telnet} to connect.
@end table
! @node Hitachi Special, , Hitachi ICE, H8/300
@subsubsection Special @value{GDBN} commands for Hitachi micros
Some @value{GDBN} commands are available only for the H8/300:
--- 10554,10560 ----
specify its hostname; @value{GDBN} uses @code{telnet} to connect.
@end table
! @node Hitachi Special
@subsubsection Special @value{GDBN} commands for Hitachi micros
Some @value{GDBN} commands are available only for the H8/300:
*************** to check which variant is currently in e
*** 10487,10493 ****
@end table
! @node H8/500, i960, H8/300, Embedded Processors
@subsection H8/500
@table @code
--- 10571,10577 ----
@end table
! @node H8/500
@subsection H8/500
@table @code
*************** memory}. The accepted values for @var{m
*** 10503,10509 ****
@end table
! @node i960, M32R/D, H8/500, Embedded Processors
@subsection Intel i960
@table @code
--- 10587,10593 ----
@end table
! @node i960
@subsection Intel i960
@table @code
*************** downloads @var{filename} to the 960 as w
*** 10556,10562 ****
* Nindy Reset:: Nindy reset command
@end menu
! @node Nindy Startup, Nindy Options, i960, i960
@subsubsection Startup with Nindy
If you simply start @code{@value{GDBP}} without using any command-line
--- 10640,10646 ----
* Nindy Reset:: Nindy reset command
@end menu
! @node Nindy Startup
@subsubsection Startup with Nindy
If you simply start @code{@value{GDBP}} without using any command-line
*************** simply start up with no Nindy connection
*** 10574,10580 ****
with an empty line. If you do this and later wish to attach to Nindy,
use @code{target} (@pxref{Target Commands, ,Commands for managing targets}).
! @node Nindy Options, Nindy Reset, Nindy Startup, i960
@subsubsection Options for Nindy
These are the startup options for beginning your @value{GDBN} session with a
--- 10658,10664 ----
with an empty line. If you do this and later wish to attach to Nindy,
use @code{target} (@pxref{Target Commands, ,Commands for managing targets}).
! @node Nindy Options
@subsubsection Options for Nindy
These are the startup options for beginning your @value{GDBN} session with a
*************** The standard @samp{-b} option controls t
*** 10617,10623 ****
port.
@c @group
! @node Nindy Reset, , Nindy Options, i960
@subsubsection Nindy reset command
@table @code
--- 10701,10707 ----
port.
@c @group
! @node Nindy Reset
@subsubsection Nindy reset command
@table @code
*************** a break is detected.
*** 10630,10636 ****
@end table
@c @end group
! @node M32R/D, M68K, i960, Embedded Processors
@subsection Mitsubishi M32R/D
@table @code
--- 10714,10720 ----
@end table
@c @end group
! @node M32R/D
@subsection Mitsubishi M32R/D
@table @code
*************** Mitsubishi M32R/D ROM monitor.
*** 10641,10647 ****
@end table
! @node M68K, M88K, M32R/D, Embedded Processors
@subsection M68k
The Motorola m68k configuration includes ColdFire support, and
--- 10725,10731 ----
@end table
! @node M68K
@subsection M68k
The Motorola m68k configuration includes ColdFire support, and
*************** ROMBUG ROM monitor for OS/9000.
*** 10692,10698 ****
@end table
! @node M88K, MIPS Embedded, M68K, Embedded Processors
@subsection M88K
@table @code
--- 10776,10782 ----
@end table
! @node M88K
@subsection M88K
@table @code
*************** BUG monitor, running on a MVME187 (m88k)
*** 10703,10709 ****
@end table
! @node MIPS Embedded, PowerPC, M88K, Embedded Processors
@subsection MIPS Embedded
@cindex MIPS boards
--- 10787,10793 ----
@end table
! @node MIPS Embedded
@subsection MIPS Embedded
@cindex MIPS boards
*************** forever because it has no way of knowing
*** 10847,10853 ****
to run before stopping.
@end table
! @node PowerPC, PA, MIPS Embedded, Embedded Processors
@subsection PowerPC
@table @code
--- 10931,10937 ----
to run before stopping.
@end table
! @node PowerPC
@subsection PowerPC
@table @code
*************** SDS monitor, running on a PowerPC board
*** 10868,10874 ****
@end table
! @node PA, SH, PowerPC, Embedded Processors
@subsection HP PA Embedded
@table @code
--- 10952,10958 ----
@end table
! @node PA
@subsection HP PA Embedded
@table @code
*************** W89K monitor, running on a Winbond HPPA
*** 10883,10889 ****
@end table
! @node SH, Sparclet, PA, Embedded Processors
@subsection Hitachi SH
@table @code
--- 10967,10973 ----
@end table
! @node SH
@subsection Hitachi SH
@table @code
*************** Hitachi SH-3 and SH-3E target systems.
*** 10906,10912 ****
@end table
! @node Sparclet, Sparclite, SH, Embedded Processors
@subsection Tsqware Sparclet
@cindex Sparclet
--- 10990,10996 ----
@end table
! @node Sparclet
@subsection Tsqware Sparclet
@cindex Sparclet
*************** run @value{GDBN}. From your Unix host,
*** 10960,10966 ****
* Sparclet Execution:: Running and debugging
@end menu
! @node Sparclet File, Sparclet Connection, Sparclet, Sparclet
@subsubsection Setting file to debug
The @value{GDBN} command @code{file} lets you choose with program to debug.
--- 11044,11050 ----
* Sparclet Execution:: Running and debugging
@end menu
! @node Sparclet File
@subsubsection Setting file to debug
The @value{GDBN} command @code{file} lets you choose with program to debug.
*************** When this happens, add the appropriate d
*** 10990,10996 ****
the @value{GDBN} commands @code{path} and @code{dir}, and execute the
@code{target} command again.
! @node Sparclet Connection, Sparclet Download, Sparclet File, Sparclet
@subsubsection Connecting to Sparclet
The @value{GDBN} command @code{target} lets you connect to a Sparclet target.
--- 11074,11080 ----
the @value{GDBN} commands @code{path} and @code{dir}, and execute the
@code{target} command again.
! @node Sparclet Connection
@subsubsection Connecting to Sparclet
The @value{GDBN} command @code{target} lets you connect to a Sparclet target.
*************** main () at ../prog.c:3
*** 11009,11015 ****
Connected to ttya.
@end example
! @node Sparclet Download, Sparclet Execution, Sparclet Connection, Sparclet
@subsubsection Sparclet download
@cindex download to Sparclet
--- 11093,11099 ----
Connected to ttya.
@end example
! @node Sparclet Download
@subsubsection Sparclet download
@cindex download to Sparclet
*************** If the code is loaded at a different add
*** 11035,11041 ****
to, you may need to use the @code{section} and @code{add-symbol-file} commands
to tell @value{GDBN} where to map the symbol table.
! @node Sparclet Execution, , Sparclet Download, Sparclet
@subsubsection Running and debugging
@cindex running and debugging Sparclet programs
--- 11119,11125 ----
to, you may need to use the @code{section} and @code{add-symbol-file} commands
to tell @value{GDBN} where to map the symbol table.
! @node Sparclet Execution
@subsubsection Running and debugging
@cindex running and debugging Sparclet programs
*************** Breakpoint 1, main (argc=1, argv=0xeffff
*** 11055,11061 ****
(gdbslet)
@end example
! @node Sparclite, ST2000, Sparclet, Embedded Processors
@subsection Fujitsu Sparclite
@table @code
--- 11139,11145 ----
(gdbslet)
@end example
! @node Sparclite
@subsection Fujitsu Sparclite
@table @code
*************** remote protocol.
*** 11069,11075 ****
@end table
! @node ST2000, Z8000, Sparclite, Embedded Processors
@subsection Tandem ST2000
@value{GDBN} may be used with a Tandem ST2000 phone switch, running Tandem's
--- 11153,11159 ----
@end table
! @node ST2000
@subsection Tandem ST2000
@value{GDBN} may be used with a Tandem ST2000 phone switch, running Tandem's
*************** sequences gets you back to the @value{GD
*** 11118,11124 ****
@kbd{@key{RET}~@key{C-d}} (Return, followed by tilde and control-D).
@end table
! @node Z8000, , ST2000, Embedded Processors
@subsection Zilog Z8000
@cindex Z8000
--- 11202,11208 ----
@kbd{@key{RET}~@key{C-d}} (Return, followed by tilde and control-D).
@end table
! @node Z8000
@subsection Zilog Z8000
@cindex Z8000
*************** conventions; for example, @w{@samp{b fpu
*** 11169,11175 ****
conditional breakpoint that suspends only after at least 5000
simulated clock ticks.
! @node Architectures, , Embedded Processors, Configurations
@section Architectures
This section describes characteristics of architectures that affect
--- 11253,11259 ----
conditional breakpoint that suspends only after at least 5000
simulated clock ticks.
! @node Architectures
@section Architectures
This section describes characteristics of architectures that affect
*************** all uses of @value{GDBN} with the archit
*** 11181,11187 ****
* MIPS::
@end menu
! @node A29K, Alpha, Architectures, Architectures
@subsection A29K
@table @code
--- 11265,11271 ----
* MIPS::
@end menu
! @node A29K
@subsection A29K
@table @code
*************** processors.
*** 11207,11218 ****
@end table
! @node Alpha, MIPS, A29K, Architectures
@subsection Alpha
See the following section.
! @node MIPS, , Alpha, Architectures
@subsection MIPS
@cindex stack on Alpha
--- 11291,11302 ----
@end table
! @node Alpha
@subsection Alpha
See the following section.
! @node MIPS
@subsection MIPS
@cindex stack on Alpha
*************** These commands are available @emph{only}
*** 11247,11253 ****
for debugging programs on Alpha or MIPS processors.
! @node Controlling GDB, Sequences, Configurations, Top
@chapter Controlling @value{GDBN}
You can alter the way @value{GDBN} interacts with you by using the
--- 11331,11337 ----
for debugging programs on Alpha or MIPS processors.
! @node Controlling GDB
@chapter Controlling @value{GDBN}
You can alter the way @value{GDBN} interacts with you by using the
*************** described here.
*** 11265,11271 ****
* Debugging Output:: Optional messages about internal happenings
@end menu
! @node Prompt, Editing, Controlling GDB, Controlling GDB
@section Prompt
@cindex prompt
--- 11349,11355 ----
* Debugging Output:: Optional messages about internal happenings
@end menu
! @node Prompt
@section Prompt
@cindex prompt
*************** Directs @value{GDBN} to use @var{newprom
*** 11291,11297 ****
Prints a line of the form: @samp{Gdb's prompt is: @var{your-prompt}}
@end table
! @node Editing, History, Prompt, Controlling GDB
@section Command editing
@cindex readline
@cindex command line editing
--- 11375,11381 ----
Prints a line of the form: @samp{Gdb's prompt is: @var{your-prompt}}
@end table
! @node Editing
@section Command editing
@cindex readline
@cindex command line editing
*************** Disable command line editing.
*** 11321,11327 ****
Show whether command line editing is enabled.
@end table
! @node History, Screen Size, Editing, Controlling GDB
@section Command history
@value{GDBN} can keep track of the commands you type during your
--- 11405,11411 ----
Show whether command line editing is enabled.
@end table
! @node History
@section Command history
@value{GDBN} can keep track of the commands you type during your
*************** Print ten commands centered on command n
*** 11418,11424 ****
Print ten commands just after the commands last printed.
@end table
! @node Screen Size, Numbers, History, Controlling GDB
@section Screen size
@cindex size of screen
@cindex pauses in output
--- 11502,11508 ----
Print ten commands just after the commands last printed.
@end table
! @node Screen Size
@section Screen size
@cindex size of screen
@cindex pauses in output
*************** Likewise, you can specify @samp{set widt
*** 11460,11466 ****
from wrapping its output.
@end table
! @node Numbers, Messages/Warnings, Screen Size, Controlling GDB
@section Numbers
@cindex number representation
@cindex entering numbers
--- 11544,11550 ----
from wrapping its output.
@end table
! @node Numbers
@section Numbers
@cindex number representation
@cindex entering numbers
*************** Display the current default base for num
*** 11507,11513 ****
Display the current default base for numeric display.
@end table
! @node Messages/Warnings, Debugging Output , Numbers, Controlling GDB
@section Optional warnings and messages
By default, @value{GDBN} is silent about its inner workings. If you are
--- 11591,11597 ----
Display the current default base for numeric display.
@end table
! @node Messages/Warnings
@section Optional warnings and messages
By default, @value{GDBN} is silent about its inner workings. If you are
*************** Displays state of confirmation requests.
*** 11583,11589 ****
@end table
! @node Debugging Output, ,Messages/Warnings, Controlling GDB
@section Optional messages about internal happenings
@table @code
@kindex set debug arch
--- 11667,11673 ----
@end table
! @node Debugging Output
@section Optional messages about internal happenings
@table @code
@kindex set debug arch
*************** Displays the current state of displaying
*** 11654,11660 ****
debugging info.
@end table
! @node Sequences, Emacs, Controlling GDB, Top
@chapter Canned Sequences of Commands
Aside from breakpoint commands (@pxref{Break Commands, ,Breakpoint
--- 11738,11744 ----
debugging info.
@end table
! @node Sequences
@chapter Canned Sequences of Commands
Aside from breakpoint commands (@pxref{Break Commands, ,Breakpoint
*************** files.
*** 11669,11675 ****
* Output:: Commands for controlled output
@end menu
! @node Define, Hooks, Sequences, Sequences
@section User-defined commands
@cindex user-defined command
--- 11753,11759 ----
* Output:: Commands for controlled output
@end menu
! @node Define
@section User-defined commands
@cindex user-defined command
*************** without asking when used inside a user-d
*** 11762,11768 ****
commands that normally print messages to say what they are doing omit the
messages when used in a user-defined command.
! @node Hooks, Command Files, Define, Sequences
@section User-defined command hooks
@cindex command hooks
@cindex hooks, for commands
--- 11846,11852 ----
commands that normally print messages to say what they are doing omit the
messages when used in a user-defined command.
! @node Hooks
@section User-defined command hooks
@cindex command hooks
@cindex hooks, for commands
*************** If an error occurs during the execution
*** 11808,11814 ****
If you try to define a hook which does not match any known command, you
get a warning from the @code{define} command.
! @node Command Files, Output, Hooks, Sequences
@section Command files
@cindex command files
--- 11892,11898 ----
If you try to define a hook which does not match any known command, you
get a warning from the @code{define} command.
! @node Command Files
@section Command files
@cindex command files
*************** without asking when used in a command fi
*** 11871,11877 ****
normally print messages to say what they are doing omit the messages
when called from command files.
! @node Output, , Command Files, Sequences
@section Commands for controlled output
During the execution of a command file or a user-defined command, normal
--- 11955,11961 ----
normally print messages to say what they are doing omit the messages
when called from command files.
! @node Output
@section Commands for controlled output
During the execution of a command file or a user-defined command, normal
*************** string are the simple ones that consist
*** 11951,11957 ****
letter.
@end table
! @node Emacs, Annotations, Sequences, Top
@chapter Using @value{GDBN} under @sc{gnu} Emacs
@cindex Emacs
--- 12035,12041 ----
letter.
@end table
! @node Emacs
@chapter Using @value{GDBN} under @sc{gnu} Emacs
@cindex Emacs
*************** environment. Users of this environment
*** 12125,12135 ****
each value is printed in its own window.
@end ignore
! @node Annotations, GDB Bugs, Emacs, Top
@chapter @value{GDBN} Annotations
@include annotate.texi
! @node GDB Bugs, Command Line Editing, Annotations, Top
@chapter Reporting Bugs in @value{GDBN}
@cindex bugs in @value{GDBN}
@cindex reporting bugs in @value{GDBN}
--- 12209,12219 ----
each value is printed in its own window.
@end ignore
! @node Annotations
@chapter @value{GDBN} Annotations
@include annotate.texi
! @node GDB Bugs
@chapter Reporting Bugs in @value{GDBN}
@cindex bugs in @value{GDBN}
@cindex reporting bugs in @value{GDBN}
*************** information that enables us to fix the b
*** 12149,12155 ****
* Bug Reporting:: How to report bugs
@end menu
! @node Bug Criteria, Bug Reporting, GDB Bugs, GDB Bugs
@section Have you found a bug?
@cindex bug criteria
--- 12233,12239 ----
* Bug Reporting:: How to report bugs
@end menu
! @node Bug Criteria
@section Have you found a bug?
@cindex bug criteria
*************** If you are an experienced user of debugg
*** 12181,12187 ****
for improvement of @value{GDBN} are welcome in any case.
@end itemize
! @node Bug Reporting, , Bug Criteria, GDB Bugs
@section How to report bugs
@cindex bug reports
@cindex @value{GDBN} bugs, reporting
--- 12265,12271 ----
for improvement of @value{GDBN} are welcome in any case.
@end itemize
! @node Bug Reporting
@section How to report bugs
@cindex bug reports
@cindex @value{GDBN} bugs, reporting
*************** things without first using the debugger
*** 12371,12387 ****
@c Use -I with makeinfo to point to the appropriate directory,
@c environment var TEXINPUTS with TeX.
! @node Command Line Editing, Using History Interactively, GDB Bugs, Top
@chapter Command Line Editing
@include rluser.texinfo
! @node Using History Interactively, Formatting Documentation, Command Line Editing, Top
@chapter Using History Interactively
@include inc-hist.texinfo
! @node Formatting Documentation, Installing GDB, Using History Interactively, Top
@appendix Formatting Documentation
@cindex @value{GDBN} reference card
--- 12455,12471 ----
@c Use -I with makeinfo to point to the appropriate directory,
@c environment var TEXINPUTS with TeX.
! @node Command Line Editing
@chapter Command Line Editing
@include rluser.texinfo
! @node Using History Interactively
@chapter Using History Interactively
@include inc-hist.texinfo
! @node Formatting Documentation
@appendix Formatting Documentation
@cindex @value{GDBN} reference card
*************** make gdb.dvi
*** 12467,12473 ****
Then give @file{gdb.dvi} to your @sc{dvi} printing program.
! @node Installing GDB, Index, Formatting Documentation, Top
@appendix Installing @value{GDBN}
@cindex configuring @value{GDBN}
@cindex installation
--- 12551,12557 ----
Then give @file{gdb.dvi} to your @sc{dvi} printing program.
! @node Installing GDB
@appendix Installing @value{GDBN}
@cindex configuring @value{GDBN}
@cindex installation
*************** let @value{GDBN} debug child processes w
*** 12587,12593 ****
* Configure Options:: Summary of options for configure
@end menu
! @node Separate Objdir, Config Names, Installing GDB, Installing GDB
@section Compiling @value{GDBN} in another directory
If you want to run @value{GDBN} versions for several host or target machines,
--- 12671,12677 ----
* Configure Options:: Summary of options for configure
@end menu
! @node Separate Objdir
@section Compiling @value{GDBN} in another directory
If you want to run @value{GDBN} versions for several host or target machines,
*************** directories, you can run @code{make} on
*** 12648,12654 ****
if they are NFS-mounted on each of the hosts); they will not interfere
with each other.
! @node Config Names, Configure Options, Separate Objdir, Installing GDB
@section Specifying names for hosts and targets
The specifications used for hosts and targets in the @code{configure}
--- 12732,12738 ----
if they are NFS-mounted on each of the hosts); they will not interfere
with each other.
! @node Config Names
@section Specifying names for hosts and targets
The specifications used for hosts and targets in the @code{configure}
*************** Invalid configuration `i986v': machine `
*** 12690,12696 ****
@code{config.sub} is also distributed in the @value{GDBN} source
directory (@file{gdb-@value{GDBVN}}, for version @value{GDBVN}).
! @node Configure Options, , Config Names, Installing GDB
@section @code{configure} options
Here is a summary of the @code{configure} options and arguments that
--- 12774,12780 ----
@code{config.sub} is also distributed in the @value{GDBN} source
directory (@file{gdb-@value{GDBVN}}, for version @value{GDBVN}).
! @node Configure Options
@section @code{configure} options
Here is a summary of the @code{configure} options and arguments that
*************** There is no convenient way to generate a
*** 12759,12765 ****
There are many other options available as well, but they are generally
needed for special purposes only.
! @node Index, , Installing GDB, Top
@unnumbered Index
@printindex cp
--- 12843,12849 ----
There are many other options available as well, but they are generally
needed for special purposes only.
! @node Index
@unnumbered Index
@printindex cp
From msnyder@cygnus.com Tue Mar 28 10:32:00 2000
From: Michael Snyder <msnyder@cygnus.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA] Avoid core dumping on corrupt stabs entry
Date: Tue, 28 Mar 2000 10:32:00 -0000
Message-id: <38E0FAD3.60B7@cygnus.com>
References: <20000327204057.A24783@cygnus.com>
X-SW-Source: 2000-03/msg00649.html
Content-length: 907
Chris Faylor wrote:
>
> Any objections to this patch? It seems to be in the spirit of the rest
> of the file.
Looks good to me. JimB?
> 2000-03-27 Christopher Faylor <cgf@cygnus.com>
>
> * partial-stab.h: Add one more check against corrupted or irregular
> stabs entry.
>
> Index: partial-stab.h
> ===================================================================
> RCS file: /cvs/cvsfiles/devo/gdb/partial-stab.h,v
> retrieving revision 2.68
> diff -u -p -r2.68 partial-stab.h
> --- partial-stab.h 1999/09/14 22:50:39 2.68
> +++ partial-stab.h 2000/03/28 01:37:53
> @@ -393,7 +393,7 @@ switch (CUR_SYMBOL_TYPE)
>
> #ifdef DBXREAD_ONLY
> /* See if this is an end of function stab. */
> - if (CUR_SYMBOL_TYPE == N_FUN && *namestring == '\000')
> + if (pst && CUR_SYMBOL_TYPE == N_FUN && *namestring == '\000')
> {
> unsigned long valu;
>
From msnyder@cygnus.com Tue Mar 28 11:15:00 2000
From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: procfs.c:proc_set_watchpoint bug fix
Date: Tue, 28 Mar 2000 11:15:00 -0000
Message-id: <38E1023A.7A8E@cygnus.com>
References: <200003072114.WAA26143@reisser.regent.e-technik.tu-muenchen.de>
X-SW-Source: 2000-03/msg00650.html
Content-length: 1093
Peter.Schauer wrote:
>
> procfs.c:proc_set_watchpoint currently declares its addr parameter as
> void *, but it is called from procfs_set_watchpoint with a CORE_ADDR addr.
> This causes problems if sizeof(CORE_ADDR) > sizeof(void *), e.g on
> Solaris 2.7 sparc.
Approved and committed.
> 2000-03-07 Peter Schauer <pes@regent.e-technik.tu-muenchen.de>
>
> * procfs.c (proc_set_watchpoint): Declare addr parameter as
> CORE_ADDR, to match call from procfs_set_watchpoint.
>
> *** gdb/procfs.c.orig Wed Mar 1 21:54:05 2000
> --- gdb/procfs.c Sun Mar 5 12:05:33 2000
> ***************
> *** 2580,2586 ****
> int
> proc_set_watchpoint (pi, addr, len, wflags)
> procinfo *pi;
> ! void *addr;
> int len;
> int wflags;
> {
> --- 2580,2586 ----
> int
> proc_set_watchpoint (pi, addr, len, wflags)
> procinfo *pi;
> ! CORE_ADDR addr;
> int len;
> int wflags;
> {
>
> --
> Peter Schauer pes@regent.e-technik.tu-muenchen.de
From msnyder@cygnus.com Tue Mar 28 11:30:00 2000
From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: breakpoint.c: Minor output fixes for hardware watchpoints
Date: Tue, 28 Mar 2000 11:30:00 -0000
Message-id: <38E1067A.119C@cygnus.com>
References: <200003072114.WAA26280@reisser.regent.e-technik.tu-muenchen.de>
X-SW-Source: 2000-03/msg00651.html
Content-length: 5447
Peter.Schauer wrote:
>
> During implementation of hardware watchpoints on Solaris, I noticed the
> following inconsistencies in breakpoint.c output between software and
> hardware breakpoints.
>
> 1) insert_breakpoints and do_enable_breakpoint now use select_and_print_frame
> to reselect frames after frame selection for watchpoint evaluation.
> Up to gdb-4.18 GDB used select_frame to reselect frames.
> I have no idea why this was done (I am unable to find a ChangeLog entry,
> perhaps this was a side effect of the HP merge), and it causes the following
> confusing output from the recurse.exp testcase:
This change did indeed come in with the HP merge, which was so
massive that we did not get justifications for every little
change. I'm going to approve backing this change out. If
the folks at HP really need it, let's get a justification
and a change that doesn't have unpleasant side effects.
Checking in this patch.
> continue
> Continuing.
> #0 recurse (a=10) at /users/pes/gdbnd/devo/gdb/testsuite/gdb.base/recurse.c:15
> 15 if (a == 1)
> Hardware watchpoint 2: b
>
> Old value = 0
> New value = 10
> recurse (a=10) at /users/pes/gdbnd/devo/gdb/testsuite/gdb.base/recurse.c:19
> 19 b *= recurse (a - 1);
> (gdb) PASS: gdb.base/recurse.exp: continue to first instance watchpoint, first time
>
> Note the extra frame output before the watchpoint trigger. This is still
> worse in other cases, where we have even more frame output (see below).
>
> 2) insert_breakpoints tries to reinsert watchpoints even if they are already
> marked for deletion at next stop, causing the following redundant output,
> again from the recurse.exp testcase:
>
> continue
> Continuing.
> #0 recurse (a=5) at /users/pes/gdbnd/devo/gdb/testsuite/gdb.base/recurse.c:20
> 20 return b;
> #0 recurse (a=5) at /users/pes/gdbnd/devo/gdb/testsuite/gdb.base/recurse.c:20
> 20 return b;
> Watchpoint 4 deleted because the program has left the block in
> which its expression is valid.
> #0 0x8048a71 in recurse (a=6) at /users/pes/gdbnd/devo/gdb/testsuite/gdb.base/recurse.c:19
> 19 b *= recurse (a - 1);
> Hardware watchpoint 4 deletedbecause the program has left the block
> in which its expression is valid.
> 0x8048a70 in recurse (a=6) at /users/pes/gdbnd/devo/gdb/testsuite/gdb.base/recurse.c:19
> 19 b *= recurse (a - 1);
> (gdb) PASS: gdb.base/recurse.exp: second instance watchpoint deleted when leaving scope
>
> Here is a patch for both problems:
>
> 2000-03-07 Peter Schauer <pes@regent.e-technik.tu-muenchen.de>
>
> * breakpoint.c (insert_breakpoints, do_enable_breakpoint): Reselect
> the saved frame silently after frame selection for watchpoint
> evaluation.
> (insert_breakpoints): Add missing space in `Hardware watchpoint
> deleted' message. Do not reinsert hardware watchpoint if it is
> already marked for deletion at next stop.
>
> *** gdb/breakpoint.c.orig Thu Feb 24 13:41:33 2000
> --- gdb/breakpoint.c Sat Mar 4 11:42:48 2000
> ***************
> *** 918,923 ****
> --- 918,924 ----
> b->type == bp_read_watchpoint ||
> b->type == bp_access_watchpoint)
> && b->enable == enabled
> + && b->disposition != del_at_next_stop
> && !b->inserted
> && !b->duplicate)
> {
> ***************
> *** 1005,1011 ****
> }
> else
> {
> ! printf_filtered ("Hardware watchpoint %d deleted", b->number);
> printf_filtered ("because the program has left the block \n");
> printf_filtered ("in which its expression is valid.\n");
> if (b->related_breakpoint)
> --- 1006,1012 ----
> }
> else
> {
> ! printf_filtered ("Hardware watchpoint %d deleted ", b->number);
> printf_filtered ("because the program has left the block \n");
> printf_filtered ("in which its expression is valid.\n");
> if (b->related_breakpoint)
> ***************
> *** 1016,1022 ****
> /* Restore the frame and level. */
> if ((saved_frame != selected_frame) ||
> (saved_level != selected_frame_level))
> ! select_and_print_frame (saved_frame, saved_level);
>
> if (val)
> return_val = val; /* remember failure */
> --- 1017,1023 ----
> /* Restore the frame and level. */
> if ((saved_frame != selected_frame) ||
> (saved_level != selected_frame_level))
> ! select_frame (saved_frame, saved_level);
>
> if (val)
> return_val = val; /* remember failure */
> ***************
> *** 7536,7543 ****
> }
>
> if (save_selected_frame_level >= 0)
> ! select_and_print_frame (save_selected_frame,
> ! save_selected_frame_level);
> value_free_to_mark (mark);
> }
> if (modify_breakpoint_hook)
> --- 7558,7564 ----
> }
>
> if (save_selected_frame_level >= 0)
> ! select_frame (save_selected_frame, save_selected_frame_level);
> value_free_to_mark (mark);
> }
> if (modify_breakpoint_hook)
>
> --
> Peter Schauer pes@regent.e-technik.tu-muenchen.de
From shebs@apple.com Tue Mar 28 12:33:00 2000
From: Stan Shebs <shebs@apple.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH] Fix texinfo problems...
Date: Tue, 28 Mar 2000 12:33:00 -0000
Message-id: <38E1171F.7651C329@apple.com>
References: <38DB1875.4B504618@cygnus.com> <38DBB937.126C95E@apple.com> <38DC6763.563424A2@cygnus.com> <200003260443.XAA26499@mescaline.gnu.org> <38E05161.9707ED26@cygnus.com>
X-SW-Source: 2000-03/msg00652.html
Content-length: 462
Andrew Cagney wrote:
> The attatched converts my botch into your patch.
> I've also dropped a copy of texinfo-3.12 into the snapshots directory.
>
> sorry,
> Andrew
>
> Stan, ok?
I didn't see your message before doing my big commit this morning,
so some of the changes are redundant. I would suggest updating
from cvs over your patched file and seeing what's left over after
the merge - the remainder should be much smaller...
Stan
From msnyder@cygnus.com Tue Mar 28 13:18:00 2000
From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches@sourceware.cygnus.com
Subject: [PATCH]: minor Makefile.in tweak
Date: Tue, 28 Mar 2000 13:18:00 -0000
Message-id: <200003282118.NAA29340@cleaver.cygnus.com>
X-SW-Source: 2000-03/msg00653.html
Content-length: 1671
Sun's 'make' on Solaris-x86 seems to work better if this
dependency is made explicitly relative to $(srcdir).
I don't know if that is a bug in VPATH handling, or what...
2000-03-28 Michael Snyder <msnyder@cleaver.cygnus.com>
* Makefile.in: anchor tui-file.h dependency to $srcdir.
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.199
diff -c -r1.199 ChangeLog
*** ChangeLog 2000/03/28 19:29:56 1.199
--- ChangeLog 2000/03/28 21:15:16
***************
*** 1,3 ****
--- 1,7 ----
+ 2000-03-28 Michael Snyder <msnyder@cleaver.cygnus.com>
+
+ * Makefile.in: anchor tui-file.h dependency to $srcdir.
+
2000-03-28 Peter Schauer <pes@regent.e-technik.tu-muenchen.de>
* procfs.c (proc_set_watchpoint): Declare addr parameter as
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.16
diff -c -r1.16 Makefile.in
*** Makefile.in 2000/03/27 06:51:30 1.16
--- Makefile.in 2000/03/28 21:15:17
***************
*** 1492,1498 ****
mac-nat.o: mac-nat.c $(defs_h) gdb_string.h
! main.o: main.c top.h $(defs_h) gdb_string.h $(event_loop_h) tui/tui-file.h
maint.o: maint.c $(defs_h) $(gdbcmd_h) $(gdbtypes_h) $(symtab_h) language.h \
$(expression_h) objfiles.h symfile.h
--- 1492,1498 ----
mac-nat.o: mac-nat.c $(defs_h) gdb_string.h
! main.o: main.c top.h $(defs_h) gdb_string.h $(event_loop_h) $(srcdir)/tui/tui-file.h
maint.o: maint.c $(defs_h) $(gdbcmd_h) $(gdbtypes_h) $(symtab_h) language.h \
$(expression_h) objfiles.h symfile.h
From tromey@cygnus.com Tue Mar 28 13:30:00 2000
From: Tom Tromey <tromey@cygnus.com>
To: gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH]: minor Makefile.in tweak
Date: Tue, 28 Mar 2000 13:30:00 -0000
Message-id: <87snxaok7a.fsf@cygnus.com>
References: <200003282118.NAA29340@cleaver.cygnus.com>
X-SW-Source: 2000-03/msg00654.html
Content-length: 637
Michael> Sun's 'make' on Solaris-x86 seems to work better if this
Michael> dependency is made explicitly relative to $(srcdir). I don't
Michael> know if that is a bug in VPATH handling, or what...
FYI, generally speaking vendor makes do not implement VPATH correctly.
For automake we decided to only support this feature with GNU make.
Some makes are almost good enough to use, if you add tweaks of one
sort or another. Sun's make is one of these, but I forget what tweaks
are required.
Anyway, I don't think gdb is required (i.e., per GNU coding standards)
to support VPATH for non-GNU makes. In case you care.
Tom
From ac131313@cygnus.com Tue Mar 28 14:03:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH] Don't trim addresses in Dwarf debug info
Date: Tue, 28 Mar 2000 14:03:00 -0000
Message-id: <38E12BD6.E6E357A4@cygnus.com>
References: <200003281624.LAA23161@zwingli.cygnus.com>
X-SW-Source: 2000-03/msg00655.html
Content-length: 712
Jim Blandy wrote:
>
> I've committed this:
>
> 2000-03-27 Jim Blandy <jimb@redhat.com>
>
> * dwarf2read.c: Revert Andrew Cagney's change of Dec 15, 1997.
> Don't include "bfd-elf.h".
> (address_significant_size): Delete variable.
> (dwarf2_build_psymtabs_hard): Don't set it, or check for
> consistency between it and the Dwarf 2 compilation unit header
> address size.
> (read_address): Don't mask off bits above
> address_significant_size.
> * Makefile.in (dwarf2read.o): Don't depend on $(elf_bfd_h).
> (elf_bfd_h): Remove variable; it's no longer used.
Jim, have you confirmed this doesn't cause any regressions?
Andrew
From ac131313@cygnus.com Tue Mar 28 14:17:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: Jim Kingdon <kingdon@redhat.com>, Stephane Carrez <Stephane.Carrez@worldnet.fr>, gdb-patches@sourceware.cygnus.com
Subject: Re: path for gdb/dwarf2read.c, support 16-bit targets in dwarf-2
Date: Tue, 28 Mar 2000 14:17:00 -0000
Message-id: <38E12EDA.386F148A@cygnus.com>
References: <38B2F3D3.54CF0AF0@worldnet.fr> <38BB5463.D6E5B75C@cygnus.com> <38C0D9D9.70987863@worldnet.fr> <38C225F3.9E236A55@cygnus.com> <bput8j8vi.fsf@rtl.cygnus.com> <38C737EE.513259B9@cygnus.com> <npk8in2h8y.fsf@zwingli.cygnus.com>
X-SW-Source: 2000-03/msg00656.html
Content-length: 1556
Jim Blandy wrote:
>
> > > The whole address_significant_size code in dwarf2read.c strikes me as
> > > a rather ugly kludge to work around bugs elsewhere in the tool chain.
> > > If someone is supplying a 32 bit pointer to GDB on a 16 bit target,
> > > shouldn't the rest of the tool chain be responsible for making sure
> > > the high bits are zero rather than expecting GDB to mask it off?
> > > Granted there might be complications here, like there are cases on
> > > MIPS where we treat an address as signed rather than unsigned, but I'm
> > > also pretty clear on whether that is actually design or just a bug. I
> > > could be wrong/persuadable, of course, and perhaps someone has a
> > > better idea of all this (in which case I'd suggest commenting
> > > arch_size at bfd/elf-bfd.h and/or expanding comments at
> > > bfd_arch_bits_per_address in bfd/archures.c).
> >
> > FYI, in the MIPS case it is a feature of the hardware. GDB has little
> > choice in the matter.
>
> Can you explain why, in the MIPS case, GCC/GAS/LD are unable to place
> correct information in the upper bits of the Dwarf addresses?
>
> (That sounds like a rhetorical question, but it's not. I'm having a
> hard time imagining why address_significant_bits was the right
> solution.)
From memory, it isn't just the dwarf address. The information comes
from two places:
o the debug info
o the raw symbol table
the former has 64 bit information. The latter (elf32) has only 32 bit
information. 64bits don't fit into a 32 bit table. GDB uses both.
enjoy,
Andrew
From msnyder@cygnus.com Tue Mar 28 14:45:00 2000
From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: infrun.c, breakpoint.c: Kludge for Solaris x86 hardware watchpoint support
Date: Tue, 28 Mar 2000 14:45:00 -0000
Message-id: <38E132C8.454C@cygnus.com>
References: <200003130947.KAA07528@reisser.regent.e-technik.tu-muenchen.de>
X-SW-Source: 2000-03/msg00657.html
Content-length: 3545
Peter.Schauer wrote:
>
> Unfortunately I'd need the following kludge to work around a Solaris x86
> kernel problem with hardware watchpoint support.
> See the comment in the patches for a description of the problem.
OK, committed (although doesn't this sort of defeat the advantage
of a hardware watchpoint?)
BTW, next time could you also include the ChangeLog entry in the diffs?
Thanks,
Michael
> 2000-03-12 Peter Schauer <pes@regent.e-technik.tu-muenchen.de>
>
> breakpoint.c, breakpoint.h (remove_hw_watchpoints): New function.
> infrun.c (resume): Remove hardware watchpoints before stepping
> when CANNOT_STEP_HW_WATCHPOINTS is nonzero.
>
> *** gdb/breakpoint.c.orig Thu Feb 24 13:41:33 2000
> --- gdb/breakpoint.c Sat Mar 4 11:42:48 2000
> ***************
> *** 1080,1085 ****
> --- 1081,1107 ----
> }
>
> int
> + remove_hw_watchpoints ()
> + {
> + register struct breakpoint *b;
> + int val;
> +
> + ALL_BREAKPOINTS (b)
> + {
> + if (b->inserted
> + && (b->type == bp_hardware_watchpoint
> + || b->type == bp_read_watchpoint
> + || b->type == bp_access_watchpoint))
> + {
> + val = remove_breakpoint (b, mark_uninserted);
> + if (val != 0)
> + return val;
> + }
> + }
> + return 0;
> + }
> +
> + int
> reattach_breakpoints (pid)
> int pid;
> {
> *** ./gdb/breakpoint.h.orig Thu Feb 3 05:14:27 2000
> --- ./gdb/breakpoint.h Sat Mar 4 11:42:48 2000
> ***************
> *** 562,567 ****
> --- 562,568 ----
> extern int insert_breakpoints PARAMS ((void));
>
> extern int remove_breakpoints PARAMS ((void));
> + extern int remove_hw_watchpoints PARAMS ((void));
>
> /* This function can be used to physically insert eventpoints from the
> specified traced inferior process, without modifying the breakpoint
> *** gdb/infrun.c.orig Thu Feb 24 13:41:46 2000
> --- gdb/infrun.c Mon Mar 13 09:35:54 2000
> ***************
> *** 296,301 ****
> --- 296,308 ----
> #define HAVE_CONTINUABLE_WATCHPOINT 1
> #endif
>
> + #ifndef CANNOT_STEP_HW_WATCHPOINTS
> + #define CANNOT_STEP_HW_WATCHPOINTS 0
> + #else
> + #undef CANNOT_STEP_HW_WATCHPOINTS
> + #define CANNOT_STEP_HW_WATCHPOINTS 1
> + #endif
> +
> /* Tables of how to react to signals; the user sets them. */
>
> static unsigned char *signal_stop;
> ***************
> *** 796,801 ****
> --- 803,820 ----
> if (step && breakpoints_inserted && breakpoint_here_p (read_pc ()))
> step = 0;
> #endif
> +
> + /* Some targets (e.g. Solaris x86) have a kernel bug when stepping
> + over an instruction that causes a page fault without triggering
> + a hardware watchpoint. The kernel properly notices that it shouldn't
> + stop, because the hardware watchpoint is not triggered, but it forgets
> + the step request and continues the program normally.
> + Work around the problem by removing hardware watchpoints if a step is
> + requested, GDB will check for a hardware watchpoint trigger after the
> + step anyway. */
> + if (CANNOT_STEP_HW_WATCHPOINTS && step && breakpoints_inserted)
> + remove_hw_watchpoints ();
> +
>
> /* Normally, by the time we reach `resume', the breakpoints are either
> removed or inserted, as appropriate. The exception is if we're sitting
>
> --
> Peter Schauer pes@regent.e-technik.tu-muenchen.de
From msnyder@cygnus.com Tue Mar 28 15:27:00 2000
From: Michael Snyder <msnyder@cygnus.com>
To: gdb-patches@sourceware.cygnus.com
Cc: pes@regent.e-technik.tu-muenchen.de
Subject: Re: RFA: infrun.c, breakpoint.c: Kludge for Solaris x86 hardware watchpoint support
Date: Tue, 28 Mar 2000 15:27:00 -0000
Message-id: <38E13FD7.38E@cygnus.com>
References: <200003130947.KAA07528@reisser.regent.e-technik.tu-muenchen.de> <38E132C8.454C@cygnus.com>
X-SW-Source: 2000-03/msg00658.html
Content-length: 215
Michael Snyder wrote:
> BTW, next time could you also include the ChangeLog entry
> in the diffs?
Oops, I stand corrected. I guess omitting the ChangeLog
from the diffs is the policy. Sorry for the confusion.
From ac131313@cygnus.com Tue Mar 28 16:53:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: [RFC] maint.c, move assignment to outside of IF expr
Date: Tue, 28 Mar 2000 16:53:00 -0000
Message-id: <38E153C6.C75B057@cygnus.com>
References: <38E04452.2D1EBEC5@cygnus.com>
X-SW-Source: 2000-03/msg00659.html
Content-length: 2628
Andrew Cagney wrote:
>
> OK?
>
> The attatched moves an assignment out of an if conditional. GCC was
> complaining about it.
> I'm guessing that the coder didn't intend to write ``=='' :-)
Oops, the GCC warnings have been quitely breeding in a corner. I've
accumulated/applied the attatched.
Andrew
Wed Mar 29 10:16:35 2000 Andrew Cagney <cagney@b1.cygnus.com>
+
+ * breakpoint.h (remove_hw_watchpoints): Add declaration.
+ * breakpoints.c (remove_hw_watchpoints): Update.
+ * maint.c (maintenance_do_deprecate): Avoid assignment within IF
+ condition.
+
Index: breakpoint.c
===================================================================
RCS file: /cvs/src/src/gdb/breakpoint.c,v
retrieving revision 1.6
diff -p -r1.6 breakpoint.c
*** breakpoint.c 2000/03/28 22:30:19 1.6
--- breakpoint.c 2000/03/29 00:47:47
*************** remove_breakpoints ()
*** 1096,1102 ****
}
int
! remove_hw_watchpoints ()
{
register struct breakpoint *b;
int val;
--- 1096,1102 ----
}
int
! remove_hw_watchpoints (void)
{
register struct breakpoint *b;
int val;
Index: breakpoint.h
===================================================================
RCS file: /cvs/src/src/gdb/breakpoint.h,v
retrieving revision 1.1.1.11
diff -p -r1.1.1.11 breakpoint.h
*** breakpoint.h 2000/02/03 04:14:27 1.1.1.11
--- breakpoint.h 2000/03/29 00:47:50
*************** extern struct breakpoint *set_breakpoint
*** 693,696 ****
--- 693,700 ----
deletes all breakpoints. */
extern void delete_command (char *arg, int from_tty);
+ /* Pull all H/W watchpoints from the target. Return non-zero if the
+ remove fails. */
+ extern int remove_hw_watchpoints (void);
+
#endif /* !defined (BREAKPOINT_H) */
Index: maint.c
===================================================================
RCS file: /cvs/src/src/gdb/maint.c,v
retrieving revision 1.6
diff -p -r1.6 maint.c
*** maint.c 2000/03/25 15:32:18 1.6
--- maint.c 2000/03/29 00:47:54
*************** maintenance_do_deprecate (char *text, in
*** 425,434 ****
if (deprecate)
{
/* look for a replacement command */
! if (start_ptr = strchr (text, '\"'))
{
start_ptr++;
! if (end_ptr = strrchr (start_ptr, '\"'))
{
len = end_ptr - start_ptr;
start_ptr[len] = '\0';
--- 425,436 ----
if (deprecate)
{
/* look for a replacement command */
! start_ptr = strchr (text, '\"');
! if (start_ptr != NULL)
{
start_ptr++;
! end_ptr = strrchr (start_ptr, '\"');
! if (end_ptr != NULL)
{
len = end_ptr - start_ptr;
start_ptr[len] = '\0';
From ac131313@cygnus.com Tue Mar 28 17:17:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [RFC] qfThreadExtraInfo -> qThreadExtraInfo
Date: Tue, 28 Mar 2000 17:17:00 -0000
Message-id: <38E15968.BE3BC597@cygnus.com>
X-SW-Source: 2000-03/msg00660.html
Content-length: 1905
This is just part one of the cleanups to the thread code. It brings
this specific query into line with the spec. Given it isn't deployed in
the field the change is ok.
I've other fixes but they aren't as urgent.
Andrew
Index: gdb/ChangeLog
Tue Mar 28 18:28:40 2000 Andrew Cagney <cagney@b1.cygnus.com>
* remote.c (remote_threads_extra_info): Replace qfThreadExtraInfo
with qThreadInfo.
Index: gdb/doc/ChangeLog
Tue Mar 28 18:28:45 2000 Andrew Cagney <cagney@b1.cygnus.com>
* gdb.texinfo (Protocol): Replace ``qfThreadExtraInfo'' with
qThreadInfo.
Index: gdb/remote.c
===================================================================
RCS file: /cvs/src/src/gdb/remote.c,v
retrieving revision 1.6
diff -p -r1.6 remote.c
*** remote.c 2000/03/21 01:22:05 1.6
--- remote.c 2000/03/28 23:57:53
*************** remote_threads_extra_info (struct thread
*** 1654,1660 ****
if (use_threadextra_query)
{
! sprintf (bufp, "qfThreadExtraInfo,%x", tp->pid);
putpkt (bufp);
getpkt (bufp, PBUFSIZ, 0);
if (bufp[0] != 0)
--- 1654,1660 ----
if (use_threadextra_query)
{
! sprintf (bufp, "qThreadExtraInfo,%x", tp->pid);
putpkt (bufp);
getpkt (bufp, PBUFSIZ, 0);
if (bufp[0] != 0)
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.9
diff -p -r1.9 gdb.texinfo
*** gdb.texinfo 2000/03/28 16:46:24 1.9
--- gdb.texinfo 2000/03/28 23:58:40
*************** respond to each reply with a request for
*** 9461,9467 ****
(lower-case el, for @code{'last'}).
@item extra thread info
! @tab @code{qfThreadExtraInfo,}@var{<id>}
@tab
@item
@tab
--- 9461,9467 ----
(lower-case el, for @code{'last'}).
@item extra thread info
! @tab @code{q}@code{ThreadExtraInfo}@code{,}@var{id}
@tab
@item
@tab
From ac131313@cygnus.com Tue Mar 28 18:32:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: shebs@apple.com
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH] Fix texinfo problems...
Date: Tue, 28 Mar 2000 18:32:00 -0000
Message-id: <38E16AB4.F6081625@cygnus.com>
References: <38DB1875.4B504618@cygnus.com> <38DBB937.126C95E@apple.com> <38DC6763.563424A2@cygnus.com> <200003260443.XAA26499@mescaline.gnu.org> <38E05161.9707ED26@cygnus.com> <38E1171F.7651C329@apple.com>
X-SW-Source: 2000-03/msg00661.html
Content-length: 4046
Stan Shebs wrote:
>
> Andrew Cagney wrote:
>
> > The attatched converts my botch into your patch.
> > I've also dropped a copy of texinfo-3.12 into the snapshots directory.
> >
> > sorry,
> > Andrew
> >
> > Stan, ok?
>
> I didn't see your message before doing my big commit this morning,
> so some of the changes are redundant. I would suggest updating
> from cvs over your patched file and seeing what's left over after
> the merge - the remainder should be much smaller...
A patch to revert the remainder is attached.
Andrew
Index: gdb/doc/ChangeLog
Tue Mar 28 16:06:22 2000 Andrew Cagney <cagney@b1.cygnus.com>
* gdb.texinfo: Revert remainder of Fri Mar 24 18:06:34 2000 Andrew
Cagney <cagney@b1.cygnus.com>. Move @chapter and @node entries
back to annotate.texi, rluser.texinfo and inc-hist.texinfo.
* annotate.texi: Update.
Index: readline/doc/ChangeLog
Tue Mar 28 16:06:22 2000 Andrew Cagney <cagney@b1.cygnus.com>
* inc-hist.texinfo, rluser.texinfo: Revert change Fri Mar 24
18:04:32 2000 Andrew Cagney <cagney@b1.cygnus.com>.
Unconditionally provide @chapter and @node.
Index: gdb/doc/annotate.texi
===================================================================
RCS file: /cvs/src/src/gdb/doc/annotate.texi,v
retrieving revision 1.4
diff -p -r1.4 annotate.texi
*** annotate.texi 2000/03/28 16:46:24 1.4
--- annotate.texi 2000/03/29 01:29:17
***************
*** 55,64 ****
@syncodeindex fn cp
- @ifclear GDBN
@node Annotations
@chapter @value{GDBN} Annotations
- @end ifclear
This chapter describes annotations in @value{GDBN}. Annotations are
designed to interface @value{GDBN} to graphical user interfaces or other
--- 55,62 ----
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.9
diff -p -r1.9 gdb.texinfo
*** gdb.texinfo 2000/03/28 16:46:24 1.9
--- gdb.texinfo 2000/03/29 01:29:56
*************** environment. Users of this environment
*** 12209,12216 ****
each value is printed in its own window.
@end ignore
- @node Annotations
- @chapter @value{GDBN} Annotations
@include annotate.texi
@node GDB Bugs
--- 12209,12214 ----
*************** things without first using the debugger
*** 12454,12467 ****
@c inc-hist.texinfo
@c Use -I with makeinfo to point to the appropriate directory,
@c environment var TEXINPUTS with TeX.
-
- @node Command Line Editing
- @chapter Command Line Editing
@include rluser.texinfo
-
-
- @node Using History Interactively
- @chapter Using History Interactively
@include inc-hist.texinfo
--- 12452,12458 ----
Index: readline/doc/inc-hist.texinfo
===================================================================
RCS file: /cvs/src/src/readline/doc/inc-hist.texinfo,v
retrieving revision 1.2
diff -p -r1.2 inc-hist.texinfo
*** inc-hist.texinfo 2000/03/24 07:30:07 1.2
--- inc-hist.texinfo 2000/03/29 01:30:01
*************** Permission is granted to copy and distri
*** 23,32 ****
into another language, under the above conditions for modified versions.
@end ignore
- @ifclear GDBN
@node Using History Interactively
@chapter Using History Interactively
- @end ifclear
@ifset BashFeatures
This chapter describes how to use the GNU History Library interactively,
--- 23,30 ----
Index: readline/doc/rluser.texinfo
===================================================================
RCS file: /cvs/src/src/readline/doc/rluser.texinfo,v
retrieving revision 1.2
diff -p -r1.2 rluser.texinfo
*** rluser.texinfo 2000/03/24 07:30:07 1.2
--- rluser.texinfo 2000/03/29 01:30:05
*************** into another language, under the above c
*** 36,45 ****
@comment If you are including this manual as an appendix, then set the
@comment variable readline-appendix.
- @ifclear GDBN
@node Command Line Editing
@chapter Command Line Editing
- @end ifclear
This chapter describes the basic features of the @sc{GNU}
command line editing interface.
--- 36,43 ----
From shebs@apple.com Tue Mar 28 19:00:00 2000
From: Stan Shebs <shebs@apple.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH] Fix texinfo problems...
Date: Tue, 28 Mar 2000 19:00:00 -0000
Message-id: <38E171AC.AB1B5AD0@apple.com>
References: <38DB1875.4B504618@cygnus.com> <38DBB937.126C95E@apple.com> <38DC6763.563424A2@cygnus.com> <200003260443.XAA26499@mescaline.gnu.org> <38E05161.9707ED26@cygnus.com> <38E1171F.7651C329@apple.com> <38E16AB4.F6081625@cygnus.com>
X-SW-Source: 2000-03/msg00662.html
Content-length: 876
Andrew Cagney wrote:
>
> Stan Shebs wrote:
> >
> > I didn't see your message before doing my big commit this morning,
> > so some of the changes are redundant. I would suggest updating
> > from cvs over your patched file and seeing what's left over after
> > the merge - the remainder should be much smaller...
>
> A patch to revert the remainder is attached.
If you could go ahead and commit these, that would be great. Seeing
them reminds me of why I had to take out the explicit links in the
first place - they didn't play nice with the inserted readline docs,
and would have required changes that couldn't have been accepted
into standard readline. So I slashed through the Gordian knot of
cross-links :-) by taking them all out...
(Clearly my next round of checkins should include a note to future
hackers about why the explicit links are not in there, eh?)
Stan
From ac131313@cygnus.com Tue Mar 28 19:50:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: GDB 5 2000-03-29
Date: Tue, 28 Mar 2000 19:50:00 -0000
Message-id: <38E17D2C.F7EB65B9@cygnus.com>
X-SW-Source: 2000-03/msg00663.html
Content-length: 6421
Below is my updated TODO list for GDB 5. I've also attatched the patch
I'm applying to TODO. You can see the gory details in the sources.
Looking at it. There are four ``must haves'' left.
For the watchpoint patches, if at least some have been addressed, I'd
like to put the rest off.
For Solaris/x86, what shape is it in?
The remainder look like must fix bugs.
Andrew
GDB 5.0: Must have
------------------
These are things that have been identifed as must-have for this
release of GDB.
--
Watch point related patches (Eli Zaretskii, Michael Snyder, ???)
Eli writes: This doesn't include the watchpoint-related patches I sent
beginning with August or September, and mentioned them again three
weeks ago. Here again are the pointers to the relevant messages:
Hardware breakpoints and watchpoints: patches
http://sourceware.cygnus.com/ml/gdb-patches/1999-q3/msg00173.html
Re: Hardware breakpoints and watchpoints: patches
http://sourceware.cygnus.com/ml/gdb-patches/1999-q3/msg00204.html
Re: Hardware breakpoints and watchpoints: patches
http://sourceware.cygnus.com/ml/gdb-patches/1999-q4/msg00200.html
Hardware watchpoints for bitfields
http://sourceware.cygnus.com/ml/gdb-patches/1999-q4/msg00201.html
--
Tom's speedups to GDB (Tom Tromey, Jim Blandy)
I believe that there was a late breaking fix that stopped a coredump.
http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00869.html
--
Solaris/x86 - which? (Nick Duffek, Peter Schauer, Michael Snyder?)
Nick D's working through patches from Michael Snyder and Peter S.
--
RFA: procfs.c: init_procfs_ops should set
procfs_ops.to_has_[all]_memory (Peter Schauer, Andrew Cagney?)
I am pretty sure that this is caused by some accidental deletion, but
procfs.c:init_procfs_ops no longer sets procfs_ops.to_has_memory and
procfs_ops.to_has_all_memory.
http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg01057.html
Wed Mar 29 13:40:40 2000 Andrew Cagney <cagney@b1.cygnus.com>
* TODO: Update GDB 5 status.
Index: TODO
===================================================================
RCS file: /cvs/src/src/gdb/TODO,v
retrieving revision 1.2
diff -u -r1.2 TODO
--- TODO 2000/03/27 10:24:58 1.2
+++ TODO 2000/03/29 03:43:21
@@ -62,26 +62,18 @@
--
-Texinfo broken/builds (Andrew Cagney, Stan Shebs)
-Cagney probably botched a fix to a botch.
+RFA: procfs.c: init_procfs_ops should set
+procfs_ops.to_has_[all]_memory (Peter Schauer, Andrew Cagney?)
---
+I am pretty sure that this is caused by some accidental deletion, but
+procfs.c:init_procfs_ops no longer sets procfs_ops.to_has_memory and
+procfs_ops.to_has_all_memory.
-x86 linux GDB and SIGALRM
- http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.html
+ http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg01057.html
--
-RFA: breakpoint.c: Minor output fixes for hardware watchpoints
- http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00558.html
-
-During implementation of hardware watchpoints on Solaris, I noticed the
-following inconsistencies in breakpoint.c output between software and
-hardware breakpoints.
-
---
-
GDB 5.0: Nice to have
---------------------
@@ -126,6 +118,12 @@
The pascal support patches nave been added to the patch data base. I
[cagney] strongly suspect that they are better suited for 5.1.
+Indent -gnu ?
+ http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00496.html
+
+2 pascal language patches inserted in database
+ http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00521.html
+
--
Programs run under GDB have SIGCHLD masked.
@@ -198,6 +196,39 @@
--
+x86 linux GDB and SIGALRM (???)
+ http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00803.html
+
+--
+
+Migrate qfThreadInfo packet -> qThreadInfo. (Andrew Cagney)
+
+Add support for packet enable/disable commands with these thread
+packets. General cleanup.
+
+[PATCH] Document the ThreadInfo remote protocol queries
+ http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00832.html
+
+[PATCH] "info threads" queries for remote.c
+ http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00831.html
+
+--
+
+MI documentation in GDB user guide. (Andrew Cagney, Elena Zannoni,
+Stan Shebs, anyone else?)
+
+> (Are there plans to make gdbmi.texi be part of the manual as well?)
+
+I'd like to see it go in there sooner rather than later too. Otherwise
+you're introducing discrepancies between the manual and the documentation,
+and everybody is confused - witness the lack of doc for the tracing
+commands still, some two years after they were added...
+
+[PATCH] GDB command-line switches and annotations docs
+ http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00639.html
+
+--
+
GDB 5.0: Won't have
-------------------
@@ -232,6 +263,33 @@
--
+Elimination of make_cleanup_func. (Andrew Cagney)
+
+make_cleanup_func elimination
+ http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00791.html
+ http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00814.html
+
+--
+
+Allow GDB to use installed regex. Think about updating regex to more
+recent version (Andrew Cagney).
+
+Re: A new patch for regex
+ http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00635.html
+
+A patch for gnu-regex
+ http://sourceware.cygnus.com/ml/gdb/2000-q1/msg00568.html
+
+--
+
+ChangeLog.mi vs ChangeLog-mi (Andrew Cagney)
+Needs further debate.
+
+Re: [PATCH] Add change-log variables to more MI files
+ http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00811.html
+
+--
+
GDB 5.0: Test results
---------------------
@@ -329,6 +387,30 @@
General Wish List
=================
+
+--
+
+GDBARCH cleanup (Andrew Cagney)
+
+The non-generated parts of gdbarch.{sh,h,c} should be separated out
+into gdbarch-utils.[hc] (Name ok).
+
+The ``info architecture'' command should be replaced with a fixed
+``set architecture'' (implemented using the command.c enum code).
+
+Document that gdbarch_init_ftype could easily fail because it didn't
+identify an architecture.
+
+--
+
+Check that GDB can handle all BFD architectures (Andrew Cagney)
+
+There should be a test that checks that BFD/GDB are in sync with
+regard to architecture changes. Something like a test that first
+queries GDB for all supported architectures and then feeds each back
+to GDB.. Anyone interested in learning how to write tests? :-)
+
+--
This list is probably not up to date, and opinions vary about the
importance or even desirability of some of the items.
From dan@cgsoftware.com Tue Mar 28 20:00:00 2000
From: dan@cgsoftware.com (Daniel Berlin+list.gdb-patches)
To: Andrew Cagney <ac131313@cygnus.com>
Cc: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: GDB 5 2000-03-29
Date: Tue, 28 Mar 2000 20:00:00 -0000
Message-id: <em8uqvcz.fsf@dan.resnet.rochester.edu>
References: <38E17D2C.F7EB65B9@cygnus.com>
X-SW-Source: 2000-03/msg00664.html
Content-length: 446
> Below is my updated TODO list for GDB 5. I've also attatched the patch
> I'm applying to TODO. You can see the gory details in the sources.
>
> Looking at it. There are four ``must haves'' left.
>
> For the watchpoint patches, if at least some have been addressed, I'd
> like to put the rest off.
>
> For Solaris/x86, what shape is it in?
>
> The remainder look like must fix bugs.
>
> Andrew
Maybe it's time to cut a branch then?
next prev parent reply other threads:[~2000-03-28 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-01 0:00 Stephane Carrez
[not found] ` <38BB5463.D6E5B75C@cygnus.com>
[not found] ` <38C0D9D9.70987863@worldnet.fr>
[not found] ` <38C225F3.9E236A55@cygnus.com>
2000-03-28 8:24 ` Jim Blandy [this message]
[not found] <38D4DCB0.88313CB2@worldnet.fr>
[not found] ` <38D5B6E0.50FF6A5E@cygnus.com>
[not found] ` <38D68C56.856CB00C@worldnet.fr>
2000-04-01 0:00 ` Andrew Cagney
[not found] ` <38D7E6BC.79543EBA@worldnet.fr>
2000-03-27 12:23 ` Jim Blandy
[not found] ` <38E06721.6D3A08CD@cygnus.com>
[not found] ` <npsnx91szl.fsf@zwingli.cygnus.com>
2000-04-01 0:00 ` Andrew Cagney
[not found] ` <npem8w42bg.fsf@zwingli.cygnus.com>
2000-04-01 0:00 ` Fernando Nasser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=npln332hbu.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=Stephane.Carrez@worldnet.fr \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=jimb@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox