./devel/gdb, Symbolic debugger for multiple language frontends

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 10.1nb2, Package name: gdb-10.1nb2, Maintainer: pkgsrc-users

The purpose of a debugger such as GDB is to allow you to see what
is going on "inside" another program while it executes--or what
another program was doing at the moment it crashed.

GDB can do four main kinds of things (plus other things in support
of these) to help you catch bugs in the act:

* Start your program, specifying anything that might affect its

* Make your program stop on specified conditions.

* Examine what has happened, when your program has stopped.

* Change things in your program, so you can experiment with
correcting the effects of one bug and go on to learn about

Required to run:
[shells/bash] [lang/python27]

Required to build:

Package options: python

Master sites: (Expand)

SHA1: 5218b83c33acd27ec4e62690baaf555503fdccd5
RMD160: 87163d96863e4923691f0c1bd34f58e30f2685e8
Filesize: 39302.073 KB

Version history: (Expand)

CVS history: (Expand)

   2020-12-04 21:45:51 by Nia Alarie | Files touched by this commit (456)
Log message:
Revbump packages with a runtime Python dep but no version prefix.

For the Python 3.8 default switch.
   2020-10-26 05:26:11 by Michael Forney | Files touched by this commit (3) | Package updated
Log message:
gdb: remove incorrect patch

This patch originates from pkgsrc-wip in order to prevent clang
warnings for adding an integer to a string literal by converting
"foo" + x to &"foo"[x]. However, when gdb was updated to \ 
7.9, the
ampersand was mistakenly dropped. The string literal was also
replaced with a variable, so there is no longer any reason for the

This caused the oappend function to be called with a char converted
to a pointer, which immediately crashes gdb whenever disassembly
is performed.
   2020-10-26 04:21:05 by Michael Forney | Files touched by this commit (1)
Log message:
gdb: use gnu++11 instead of c++11

gdb makes use of typeof in gdbsupport/gdb_proc_service.h, which is
disabled with -std=c++11 to prevent symbol collision.
   2020-10-24 20:22:08 by Kamil Rytarowski | Files touched by this commit (8)
Log message:
gdb: Upgrade to 10.1

October 24th, 2020: GDB 10.1 Released!

    The latest version of GDB, version 10.1, is available for download.

    This version of GDB includes the following changes and enhancements:

        Support for debugging new targets:
            BPF (bpf-unknown-none)
        GDBserver support for the following targets:
            ARC GNU/Linux
            RISC-V GNU/Linux
        Multi-target debugging support (experimental)
        Support for debuginfod, an HTTP server for distributing ELF/DWARF \ 
debugging information as well as source code.
        Support for debugging a 32-bit Windows program using a 64-bit Windows GDB.
        Support for building GDB with GNU Guile 3.0 and 2.2 (in addition to 2.0)
        Improved performance during startup through the use of threading during \ 
symbol table loading (an optional feature in GDB 9, now enabled by default in \ 
GDB 10).
        Various enhancements to the Python and Guile APIs
        Various TUI Mode fixes and enhancements.
        Other miscellaneous enhancements:
            Detection when attaching to a process of a mismatch between this \ 
process and the executable previously loaded into GDB.
            Support for default arguments for "alias" commands.
        GDBserver support for the following host triplets has been removed:

    See the NEWS file for a more complete and detailed list of what this release \ 


From: 	Joel Brobecker
Subject: 	GDB 9.1 released!
Date: 	Sat, 8 Feb 2020 18:56:59 +0400 (+04)

GDB 9.1 includes the following changes and enhancements:

* Building GDB and GDBserver now requires GNU make >= 3.82.

* If you choose to build GDB without using the GNU readline version bundled
  with the GDB sources, building GDB new requires GNU readline >= 7.0.

* Removed targets and native configurations:
  - GDB no longer supports debugging the Cell Broadband Engine;
  - GDB no longer supports Solaris 10.

* New TI PRU Simulator (pru-*-elf).

* Python Enhancements:
  - GDB can now be compiled with Python 3 on Windows;
  - Various Python API enhancements;

* Usability enhancements:
  - [experimental] Multithreaded symbol loading for higher performance
    (turned off by default, use 'maint set worker-threads unlimited'
    to turn this feature on);
  - Command names can now use the '.' character;
  - GDB can now place breakpoints on nested functions and subroutines
    in Fortran;
  - GDB now shows the Ada task names at more places, e.g. in task switching
  - Styling enhancements to various commands to improve readability.
  - GDB now has a standard infrastructure to support dash-style command
    options ('-OPT').  One benefit is that commands that use it can
    easily support completion of command line arguments. Try "CMD
    -[TAB]" or "help CMD" to find options supported by a command. \ 
    time, we intend to migrate most commands to this infrastructure.

* Enhancements to existing commands:
  - "printf" and "eval" can now print C-style and Ada-style \ 
     without calling functions in the program;
  - "info sources" has been enhance to allow only printing files
    whose name match a REGEXP;
  - New value "presence" for the "set print frame-arguments" \ 
    to only indicate the presence of arguments with '...' instead
    of printing the argument names and values;
  - The "focus", "winheight", "+", "-", \ 
">", "<" TUI commands are
    now case sensitive;
  - New options support for the following commands that allow overriding
    a number of relevant global settings (as set by e.g. "set print
    [...]" commands): "print", "compile print", \ 
"backtrace", "frame
    apply", "tfaas", "faas";
  - "info types" support for "-q" to disable printing of \ 
some header
  - In settings, "unlimited" can now be abbreviated with "u".

* New commands:
  - "define-prefix" to define user-defined prefix commands;
  - "|" or "pipe" to execute a command and send its output to
    a shell command.
  - "with" to run a given command with a setting temporarily changed
    to a given value;
  - "set may-call-functions" to control whether subprogram can be
    called from GDB;
  - "set print finish [on|off]" to control whether the returned value
    should be printed when using the "finish" command;
  - "set print max-depth" to simplify the printing of deeply nested
  - "set print raw-values [on|off]" to turn on and off pretty printers;
  - "set logging debugredirect [on|off]" to control whether to redirect
    debug output to the log file;
  - Various new "set style" commands;
  - "set print frame-info [...]" to control what information to print
    when printing a frame.
  - "set tui compact-source" to enable the "compact" mode \ 
for the TUI
    source window;
  - "info modules [...]" to query information about Fortran modules;
  - The "set/show print raw-frame-arguments" commands replace
    the "set/show print raw frame-arguments" (now with a dash instead of
    a space). The latter is now deprecated and may be removed in
    a future release.

* New GDB/MI commands
  - "-complete" to list possible completions;
  - "-catch-throw", "-catch-rethrow", and \ 
"-catch-catch", the GDB/MI
    equivalent of the "catch throw", "catch rethrow", and \ 
"catch catch"
    commands (respectively);
  - "-symbol-info-functions", "-symbol-info-types", and
    "-symbol-info-variables", the GDB/MI equivalent of the "info \ 
    "info types", and "info variables" commands (respectively);
  - "-symbol-info-modules", "-symbol-info-module-functions",
    and "-symbol-info-module-variables", the GDB/MI equivalent of
    "info modules", "info module functions" and "info \ 
module variables".

* Other MI changes
  - The default version of the MI interpreter is now 3 (-i=mi3);
  - The output of information about multi-location breakpoints (which is
    syntactically incorrect in MI 2) has changed in MI 3;
  - Backtraces and frames include a new optional field "addr_flags".

* Several new builtin convenience variables
  - $_gdb_major and $_gdb_minor;
  - $_gdb_setting, $_gdb_setting_str, $_gdb_maint_setting and
  - $_cimag and $_creal
  - $_shell_exitcode and $_shell_exitsignal

* Miscellaneous enhancements:
  - Support for a new configure option "--with-system-gdbinit-dir",
    where system gdbinit files are to be loaded from at startup;
  - 'thread-exited' event is now available in the annotations interface;
  - The TUI SingleKey keymap is now named "SingleKey" (requires
    GNU readline >= 8.0).

For a complete list and more details on each item, please see the gdb/NEWS
file, available at:
https://sourceware.org/git/gitweb.cgi?p … .1-release
   2020-10-07 06:34:01 by Michael Forney | Files touched by this commit (4)
Log message:
gdb: fix installation of gcore.1 on platforms that support gcore

Previously, gcore.1 was only installed on Linux due to an omission
in gdb/doc/Makefile.in. This caused file-check errors on Linux since
gcore.1 was not mentioned in PLIST.common.

To fix this, apply upstream commit [0] so that gcore.1 is installed
whenever gcore is.

[0] \ 
https://sourceware.org/git/?p=binutils- … e1d232392c
   2020-10-06 23:13:39 by Michael Forney | Files touched by this commit (2)
Log message:
gdb: make python files in PLIST conditional on python option

These files are only installed when python support is enabled. This
issue was already fixed for devel/gdb7 by micha, so apply the same
fix here.
   2020-08-31 20:13:29 by Thomas Klausner | Files touched by this commit (3631) | Package updated
Log message:
*: bump PKGREVISION for perl-5.32.
   2020-08-27 15:11:18 by Kamil Rytarowski | Files touched by this commit (1)
Log message:
gdb: Adapt to out-of-sources build

Requested by newer releases of GDB.