public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/25956] Hardcoded colors remain
Date: Thu, 15 Apr 2021 09:34:30 +0000	[thread overview]
Message-ID: <bug-25956-4717-djVTWiIXxz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25956-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=25956

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=92e4e97a9f569bf23b0f74479f32280c1f24cc6b

commit 92e4e97a9f569bf23b0f74479f32280c1f24cc6b
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Date:   Fri Sep 25 16:28:05 2020 +0100

    gdb: process early initialization files and command line options

    Adds the ability to process commands at a new phase during GDB's
    startup.  This phase is earlier than the current initialisation file
    processing, before GDB has produced any output.

    The number of commands that can be processed at this early stage will
    be limited, and it is expected that the only commands that would be
    processed at this stage will relate to some of the fundamentals of how
    GDB starts up.

    Currently the only commands that it makes sense to add to this early
    initialization file are those like 'set style version ....' as the
    version string is displayed during startup before the standard
    initialization files are parsed.  As such this commit fully resolved
    bug cli/25956.

    This commit adds a mechanism to execute these early initialization
    files from a users HOME directory, as well as some corresponding
    command line flags for GDB.

    The early initialization files that GDB will currently check for are
    ~/.config/gdb/gdbearlyinit (on Linux like systems) or ~/.gdbearlyinit
    if the former is not found.

    The output of 'gdb --help' has been extended to include a list of the
    early initialization files being processed.

    gdb/ChangeLog:

            PR cli/25956
            * NEWS: Mention new early init files and command line options.
            * config.in: Regenerate.
            * configure: Regenerate.
            * configure.ac: Define GDBEARLYINIT.
            * main.c (get_earlyinit_files): New function.
            (enum cmdarg_kind): Add CMDARG_EARLYINIT_FILE and
            CMDARG_EARLYINIT_COMMAND.
            (captured_main_1): Add support for new command line flags, and for
            processing startup files.
            (print_gdb_help): Include startup files in the output.

    gdb/doc/ChangeLog:

            PR cli/25956
            * gdb.texinfo (File Options): Mention new command line options.
            (Startup): Discuss when early init files are processed.
            (Initialization Files): Add description of early init files.
            (Output Styling): Update description of 'version' style.
            (gdb man): Mention early init files.

    gdb/testsuite/ChangeLog:

            PR cli/25956
            * gdb.base/early-init-file.c: New file.
            * gdb.base/early-init-file.exp: New file.
            * lib/gdb-utils.exp (style): Handle style 'none'.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-04-15  9:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 10:22 [Bug tui/25956] New: " jengelh at inai dot de
2020-06-06 15:01 ` [Bug tui/25956] " tromey at sourceware dot org
2020-08-09 18:55 ` [Bug cli/25956] " tromey at sourceware dot org
2021-01-22 19:09 ` cvs-commit at gcc dot gnu.org
2021-04-15  9:34 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-15 20:11 ` tromey at sourceware dot org

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=bug-25956-4717-djVTWiIXxz@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).