Lines Matching +refs:gdb +refs:breakpoints +refs:buffer
3 @include gdb-cfg.texi
260 @cindex breakpoints
265 There are two main ways to implement breakpoints; either as ``hardware''
266 breakpoints or as ``software'' breakpoints.
268 @cindex hardware breakpoints
270 Hardware breakpoints are sometimes available as a builtin debugging
283 breakpoints somehow; for instance, a ROM monitor may do its own
284 software breakpoints. So although these are not literally ``hardware
285 breakpoints'', from @value{GDBN}'s point of view they work the same;
289 Since they depend on hardware resources, hardware breakpoints may be
291 start trying to set software breakpoints. (On some architectures,
294 breakpoints and watchpoints. On those platforms, @value{GDBN} prints
297 @cindex software breakpoints
298 Software breakpoints require @value{GDBN} to do somewhat more work.
342 stepping. This is done with a few specialized internal breakpoints,
357 Watchpoints are a special kind of breakpoints (@pxref{Algorithms,
358 breakpoints}) which break when data is accessed rather than when some
387 breakpoints and for watchpoints, so setting too many hardware
388 breakpoints might cause watchpoint insertion to fail.
475 is generally not valid when hardware breakpoints are used, but since
518 support for watchpoints and hardware-assisted breakpoints. This
656 These functions insert and remove hardware-assisted breakpoints. The
707 hooks and gdb-events. Unfortunately, none of these paradigms was
1113 same buffer twice.
1175 @file{breakpoints.c} file.
1421 Observer - @file{gdb-events.h}.
1427 Library - @file{gdb.h}
1438 As an observer (using @file{gdb-events}) receiving notifications from
1450 before responding to a @file{gdb-event} by making a query.
1488 @subheading Observer - @file{gdb-events.h}
1489 @file{gdb-events} provides the client with a very raw mechanism that can
1510 @subheading Library - @file{gdb.h}
1797 refers to addresses (symbol tables and breakpoints at least) needs to be
2076 @item gdb/config/@var{arch}/@var{xyz}.mh
2088 @item gdb/config/@var{arch}/xm-@var{xyz}.h
2090 gdb on machine @var{xyz}. Those definitions and includes are now
2169 which are ``sourced'' by gdb. It must be possible to open files in binary
2174 The default value of the prompt string (normally @code{"(gdb) "}).
2499 @var{buf} refers to a buffer in @value{GDBN}'s memory, not the
2515 @var{buf} refers to a buffer in @value{GDBN}'s memory, not the
2647 (gdb) ptype short_ptr_var
2661 Representations}. See also @uref{http://www.gnu.org/software/gdb/bugs/,
2663 @uref{http://sources.redhat.com/gdb/current/ari/, ARI Index} for more
2723 This is the size a @code{struct value}'s buffer will have, holding that
2736 should always be @code{DEPRECATED_REGISTER_VIRTUAL_TYPE (@var{reg})}. The buffer
2751 should always be @code{DEPRECATED_REGISTER_VIRTUAL_TYPE (@var{reg})}. The buffer
2770 @uref{http://sources.redhat.com/gdb/current/ari/, A.R. Index} and
2771 @uref{http://www.gnu.org/software/gdb/bugs, Bug Tracking Database} for
2813 @var{type}. The buffer at @var{from} holds the register's value in raw
2814 format; the converted value should be placed in the buffer at @var{to}.
2981 Insert or remove memory based breakpoints. Reasonable defaults
3063 library in which breakpoints cannot be set and so should be disabled.
3508 @var{insert_breapoints_p}) breakpoints at each possible destinations of
3695 re-inserting the breakpoint. However, permanent breakpoints are
3930 @item gdb/config/@var{arch}/@var{ttt}.mt
3941 @item gdb/@var{ttt}-tdep.c
3949 @item gdb/@var{arch}-tdep.c
3950 @itemx gdb/@var{arch}-tdep.h
3956 @item gdb/config/@var{arch}/tm-@var{ttt}.h
3963 @item gdb/config/@var{arch}/tm-@var{arch}.h
4195 do breakpoints. Everything else is unnecessary for the proper operation
4198 From reading the stub, it's probably not obvious how breakpoints work.
4219 @item gdb/config/@var{arch}/@var{xyz}.mh
4235 @item gdb/config/@var{arch}/nm-@var{xyz}.h
4240 @item gdb/@var{xyz}-nat.c
4849 finish by printing a newline, to flush the wrap buffer, before switching
4908 functions such as @code{sprintf} are very prone to buffer overflow
4916 @samp{--enable-gdb-build-warnings=,-Werror} when building @value{GDBN}.
4917 The exceptions are listed in the file @file{gdb/MAINTAINERS}.
5137 of @value{GDBN}) must be added to @file{gdb/config/djgpp/fnchange.lst}.
5364 To configure @value{GDBN} itself, edit @file{gdb/configure.host} to recognize
5366 desired target is already available) also edit @file{gdb/configure.tgt},
5371 @file{gdb/configure.host} originally needed to be modified when either a
5389 @file{gdb/version.in} and takes one of the following forms:
5477 @file{gdb/version.in} to include a vendor unique alphabetic identifier
5503 @email{gdb-patches@@sources.redhat.com, the @value{GDBN} patches
5522 The @value{GDBN} module @code{gdb} should be specified when creating a
5526 The file @file{gdb/version.in} shall be modified so that it identifies
5546 cvs rtag @var{owner}_@var{name}-@var{YYYYMMDD}-branchpoint gdb
5548 @var{owner}_@var{name}-@var{YYYYMMDD}-branch gdb
5556 cvs rtag @var{owner}_@var{name}-@var{yyyymmdd}-mergepoint gdb
5574 @cindex making a new release of gdb
5583 The @file{gdb/MAINTAINERS} file still holds.
5586 trunk. If this isn't possible, mentioning it in the @file{gdb/PROBLEMS}
5623 Post the proposal on @email{gdb@@sources.redhat.com, the GDB mailing
5629 Post the proposal on @email{gdb-announce@@sources.redhat.com, the GDB
5659 @file{gdb/PROBLEMS} file.
5661 @subheading Prompt for @file{gdb/NEWS}
5667 @subheading Review @file{gdb/README}
5670 @file{gdb/README} looking for anything that can be improved. The
5689 @uref{http://sources.redhat.com/gdb/ari,,A.R.I.} is an @code{awk} script
5701 The targets are listed in @file{gdb/MAINTAINERS}.
5754 -r gdb_$V-branch src/gdb/version.in
5756 -r gdb_5_2-branch src/gdb/version.in
5758 U src/gdb/version.in
5759 $ cd src/gdb
5816 @email{gdb-announce@@sources.redhat.com, GDB Announcement mailing list}
5818 @email{gdb@@sources.redhat.com, GDB Discsussion mailing list} and
5819 @email{gdb-testers@@sources.redhat.com, GDB Discsussion mailing list}
5862 @email{gdb-patches@@sources.redhat.com}.
5896 $ for m in gdb insight dejagnu
5917 @item gdb/NEWS
5925 $ emacs gdb/src/gdb/NEWS
5930 $ cp gdb/src/gdb/NEWS insight/src/gdb/NEWS
5931 $ cp gdb/src/gdb/ChangeLog insight/src/gdb/ChangeLog
5934 @item gdb/README
5948 $ emacs gdb/src/gdb/README
5953 $ cp gdb/src/gdb/README insight/src/gdb/README
5954 $ cp gdb/src/gdb/ChangeLog insight/src/gdb/ChangeLog
5965 @item gdb/version.in
5968 $ echo $v > gdb/src/gdb/version.in
5969 $ cat gdb/src/gdb/version.in
5971 $ emacs gdb/src/gdb/version.in
5976 $ cp gdb/src/gdb/version.in insight/src/gdb/version.in
5977 $ cp gdb/src/gdb/ChangeLog insight/src/gdb/ChangeLog
5983 @code{AM_INIT_AUTOMAKE}. Tweak it to read something like gdb-5.1.91.
6005 $ for m in gdb insight
6016 $ for m in gdb insight
6030 $ ( cd gdb/src && cvs -f -q -n update )
6032 ? gdb-5.1.91.tar
6035 M gdb/ChangeLog
6036 M gdb/NEWS
6037 M gdb/README
6038 M gdb/version.in
6044 @emph{Don't worry about the @file{gdb.info-??} or
6045 @file{gdb/p-exp.tab.c}. They were generated (and yes @file{gdb.info-1}
6055 dejagnu/ dejagnu-gdb-5.2.tar.bz2 gdb/ gdb-5.2.tar insight/ insight-5.2.tar
6056 $ for m in gdb insight
6080 $ bunzip2 < gdb-5.2.tar.bz2 | tar xpf -
6081 $ cd gdb-5.2
6085 $ ./gdb/gdb ./gdb/gdb
6086 GNU gdb 5.2
6088 (gdb) b main
6090 (gdb) run
6091 Starting program: /tmp/gdb-5.2/gdb/gdb
6095 (gdb) print args
6097 (gdb)
6113 @uref{ftp://sources.redhat.com/pub/gdb/snapshots/branch}
6115 Notify the relevant mailing lists ( @email{gdb@@sources.redhat.com} and
6116 @email{gdb-testers@@sources.redhat.com} that the candidate is available.
6128 $ cp *.bz2 *.gz ~ftp/pub/gdb/old-releases/
6129 $ cp *.bz2 *.gz ~ftp/pub/gdb/releases
6137 $ cd ~ftp/pub/gdb/releases
6188 ~ftp/pub/gdb/releases/gdb-5.2.tar.bz2 \
6190 /www/sourceware/htdocs/gdb/download/onlinedocs \
6191 gdb
6199 ~ftp/pub/gdb/releases/gdb-5.2.tar.bz2 \
6201 /www/sourceware/htdocs/gdb/download/ari \
6202 gdb
6215 @file{~ftp/gnu/gdb}.
6223 @email{gdb-announce@@sources.redhat.com, GDB Announcement mailing list}
6228 @email{bug-gdb@@gnu.org, GDB Bug Report mailing list}
6241 @file{gdb/ChangeLog}
6243 @file{gdb/version.in}
6245 @file{gdb/NEWS}
6247 @file{gdb/README}
6258 $ ( cd insight/src/gdb && cvs -f -q update )
6271 @subsubheading Restart @file{gdb/version.in}
6273 If @file{gdb/version.in} does not contain an ISO date such as
6288 Post a revised release schedule to @email{gdb@@sources.redhat.com, GDB
6333 === gdb Summary ===
6381 UNRESOLVED: gdb.base/example.exp: This test script does not work on a remote host.
6387 The testsuite is entirely contained in @file{gdb/testsuite}. While the
6391 @file{testsuite/lib/gdb.exp} contains common utility procs useful for
6396 The tests themselves are to be found in @file{testsuite/gdb.*} and
6409 @item gdb.base
6416 @item gdb.@var{lang}
6418 @file{gdb.cp} and @file{gdb.java}.
6420 @item gdb.@var{platform}
6422 (host or target), such as HP-UX or eCos. Example is @file{gdb.hp}, for
6425 @item gdb.@var{compiler}
6429 imagine a @file{gdb.gcc}, for tests of @value{GDBN}'s handling of GCC
6432 @item gdb.@var{subsystem}
6434 instance, @file{gdb.disasm} exercises various disassemblers, while
6435 @file{gdb.stabs} tests pathways through the stabs symbol reader.
6447 instance, @file{gdb.base/exprs.exp} defines a @code{test_expr} that
6548 @cindex @code{bug-gdb} mailing list
6550 on @code{bug-gdb}. But @emph{never} post a generic question like ``I was
6563 debugged in another. Rather than typing the command @kbd{@w{./gdb
6564 ./gdb}}, which works on Suns and such, you can copy @file{gdb} to
6565 @file{gdb2} and then type @kbd{@w{./gdb ./gdb2}}.
6569 gdb easier. The @code{info} command, when executed without a subcommand
6570 in a @value{GDBN} being debugged by gdb, will pop you back up to the top level
6571 gdb. See @file{.gdbinit} for details.
6615 needed to the manuals (@file{gdb/doc/gdb.texinfo} or
6616 @file{gdb/doc/gdbint.texinfo}). If there are a lot of changes for a
6645 @email{gdb-patches@@sources.redhat.com, the @value{GDBN} maintainers}.