Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Orgad Shaneh <orgads@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix python compatibility with old versions of GDB
Date: Mon, 12 Jun 2017 04:31:00 -0000	[thread overview]
Message-ID: <CAGHpTB+Z4JMU2YnHOpZGz72+ugmkuGcJJ1KVipegMVpQAZ-3qA@mail.gmail.com> (raw)
In-Reply-To: <eed1cfcbc891384eb5cdaef446ba50d9@polymtl.ca>

On Mon, Jun 12, 2017 at 12:09 AM, Simon Marchi <simon.marchi@polymtl.ca> wrote:
> On 2017-06-11 19:48, Orgad Shaneh wrote:
>>
>> If data-directory is shared between various version of GDB, it should
>> work for all of them.
>>
>> There are several hasattr conditions that enable this kind of
>> compatibility.
>>
>> RegexpCollectionPrettyPrinter was missing a check that enables it to
>> work with GDB prior to 7.9, when Type.name was introduced.
>
>
> Hi Orgad,
>
> I still don't understand what problem this is trying to fix.  It looks like
> you want to make older versions of GDB work with newer versions of the
> Python scripts in the data directory.  I am not sure this is what we want.
> If you want multiple version of GDB in parallel on a system, they should all
> be compiled with a different --prefix, and they will all get their own
> data-directory.  We should only expect a certain version of the data
> directory to be compatible with the version of GDB it was shipped with.  Or
> am I missing some use case where this is not true?

Hi,

Practically the data-directory is mostly backwards-compatible, except this
small part which I found (there might be others which I didn't find). With this
patch, I'm able to run GDB 7.8 with the latest data-directory.

Is there a reason not to accept it?

- Orgad


  reply	other threads:[~2017-06-12  4:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-11 17:48 Orgad Shaneh
2017-06-11 21:09 ` Simon Marchi
2017-06-12  4:31   ` Orgad Shaneh [this message]
2017-06-13 11:23     ` Simon Marchi
2017-06-13 12:12       ` Tom Tromey
2017-06-13 12:29         ` Phil Muldoon
2017-06-13 14:44         ` Eli Zaretskii
2017-06-13 17:29           ` Simon Marchi
2017-06-13 17:47             ` Matt Rice
2017-06-13 18:42               ` Tom Tromey
2017-06-13 19:33                 ` Eli Zaretskii
2017-06-13 19:30             ` Eli Zaretskii
2017-06-13 12:53       ` Paul.Koning

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=CAGHpTB+Z4JMU2YnHOpZGz72+ugmkuGcJJ1KVipegMVpQAZ-3qA@mail.gmail.com \
    --to=orgads@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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