Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2] gdb: Allow more control over where to find python libraries
Date: Thu, 20 Feb 2020 19:22:00 -0000	[thread overview]
Message-ID: <20200220192250.GD3317@embecosm.com> (raw)
In-Reply-To: <878skxnqib.fsf@tromey.com>

* Tom Tromey <tromey@adacore.com> [2020-02-20 09:59:56 -0700]:

> >>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
> 
> Andrew> The only change since v1 is rewording of the commit message to make
> Andrew> the aim of the patch clearer.
> 
> FWIW, we have a similar situation; one additional thing we do is arrange
> to call Py_SetPythonHome to ensure that the user's PYTHONPATH doesn't
> break gdb.
> 
> It would be good if the standard gdb did this (I think someone filed
> something like this in bugzilla), but I'm not sure it can be done in a
> way that's consistent with gdb's other goals, like relocatability.

I suspect these bugs:

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

are the ones.

I'll need to think a bit more about what the implications are of
making this change...

Thanks,
Andrew


      reply	other threads:[~2020-02-20 19:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 16:46 [PATCH] " Andrew Burgess
2020-02-06 18:31 ` Eli Zaretskii
2020-02-19 15:53   ` Andrew Burgess
2020-02-19 15:57     ` Eli Zaretskii
2020-02-07 17:58 ` Simon Marchi
2020-02-08  0:22   ` Andrew Burgess
2020-02-19 16:27 ` [PATCHv2] " Andrew Burgess
2020-02-19 17:09   ` Eli Zaretskii
2020-02-20 17:00   ` Tom Tromey
2020-02-20 19:22     ` Andrew Burgess [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=20200220192250.GD3317@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.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