public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/3] [RFC] Load gdbinit files from a directory
Date: Thu, 12 Sep 2019 22:14:00 -0000	[thread overview]
Message-ID: <CAPTJ0XH1bFmze7KEuHffYqYkvB2HoKmKx3Nee4Y8FdtLq6BToA@mail.gmail.com> (raw)
In-Reply-To: <c66757d3-68ed-524e-c6e3-d3260019cc43@redhat.com>

On Mon, Aug 26, 2019 at 8:31 AM Pedro Alves <palves@redhat.com> wrote:
>
> On 8/25/19 11:23 PM, Christian Biesinger via gdb-patches wrote:
> > On Wed, Aug 21, 2019 at 2:13 PM Pedro Alves <palves@redhat.com> wrote:
> >>
> >> On 8/20/19 11:17 PM, Christian Biesinger via gdb-patches wrote:
> >>> This patch series is some refactoring and then a patch to load gdbinit
> >>> files from a directory, instead of only allowing a single file.
> >>>
> >>> Fedora ships a system gdbinit file that does something similar; this
> >>> does this by default and also works if Python is disabled.
> >>
> >> Note that Fedora won't be able to replace the current mechanism with
> >> this, because it also loads Python files from the dir:
> >
> > Hi Pedro,
> >
> > I've looked at the code more closely now, and it already uses the
> > "source" command for loading the system gdbinit file(s). So, Fedora
> > should be able to use it, I think?
>
> Are you sourcing every file in the directory irrespective of
> filename / filename extension?  Not sure that's a good idea.

I sent an updated version of the patch that limits files to *.gdb and
any other supported scripting languages (so .py/.scm right now)

Christian

      reply	other threads:[~2019-09-12 22:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 22:17 Christian Biesinger via gdb-patches
2019-08-20 22:18 ` [PATCH 1/3] Refactor get_init_files to use std::string Christian Biesinger via gdb-patches
2019-08-21 17:13   ` Sergio Durigan Junior
2019-08-21 17:29     ` Christian Biesinger via gdb-patches
2019-08-21 17:31       ` [PATCH 1/3 v2] " Christian Biesinger via gdb-patches
2019-08-21 17:34       ` [PATCH 1/3] " Sergio Durigan Junior
2019-08-20 22:18 ` [PATCH 3/3] Load system gdbinit files from a directory Christian Biesinger via gdb-patches
2019-08-21 17:32   ` Sergio Durigan Junior
2019-08-26  0:25     ` Christian Biesinger via gdb-patches
2019-08-26  0:33       ` [PATCH 3/3 v2] " Christian Biesinger via gdb-patches
2019-08-26  7:22         ` Eli Zaretskii
2019-09-12 22:12           ` Christian Biesinger via gdb-patches
2019-09-24 16:30             ` [PATCH 3/3 v3] " Christian Biesinger via gdb-patches
2019-10-03 18:42               ` Christian Biesinger via gdb-patches
2019-10-13  1:19                 ` Christian Biesinger via gdb-patches
2019-08-21 18:15   ` [PATCH 3/3] " Sergio Durigan Junior
2019-08-21 18:46     ` Christian Biesinger via gdb-patches
2019-08-20 22:18 ` [PATCH 2/3] Factor out the code to do the datadir-relocation for gdbinit Christian Biesinger via gdb-patches
2019-08-21 17:19   ` Sergio Durigan Junior
2019-08-21 17:44     ` Christian Biesinger via gdb-patches
2019-08-21 17:44       ` [PATCH 2/3 v2] " Christian Biesinger via gdb-patches
2019-08-21 17:47       ` [PATCH 2/3] " Sergio Durigan Junior
2019-08-21 18:08         ` Christian Biesinger via gdb-patches
2019-08-21 18:10           ` Sergio Durigan Junior
2019-08-21 18:13 ` [PATCH 0/3] [RFC] Load gdbinit files from a directory Pedro Alves
2019-08-21 18:33   ` Christian Biesinger via gdb-patches
2019-08-21 18:54     ` Sergio Durigan Junior
2019-08-25 22:24   ` Christian Biesinger via gdb-patches
2019-08-26 13:31     ` Pedro Alves
2019-09-12 22:14       ` Christian Biesinger via gdb-patches [this message]

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=CAPTJ0XH1bFmze7KEuHffYqYkvB2HoKmKx3Nee4Y8FdtLq6BToA@mail.gmail.com \
    --to=gdb-patches@sourceware.org \
    --cc=cbiesinger@google.com \
    --cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).