public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Paul Koning <paulkoning@comcast.net>
To: vincent Dupaquis <v.dupaquis@trusted-objects.com>
Cc: gdb@sourceware.org
Subject: Re: Getting access to environement variables
Date: Fri, 5 Feb 2021 09:06:58 -0500	[thread overview]
Message-ID: <54B2CC51-8AA2-43AE-95F6-80F5B4BA8128@comcast.net> (raw)
In-Reply-To: <83736f95-5415-5963-12e7-36466185cef4@trusted-objects.com>



> On Feb 5, 2021, at 4:58 AM, vincent Dupaquis <v.dupaquis@trusted-objects.com> wrote:
> 
>     Hello,
> 
>     I would like to point-out a possibly missing feature, which is the
> possibility of accessing ENV variables in GDB commands.

Assuming your GDB is built with Python scripting included, you can do it via Python; "import os" then access environment variables as elements of dictionary "os.environ".

	paul


  reply	other threads:[~2021-02-05 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05  9:58 vincent Dupaquis
2021-02-05 14:06 ` Paul Koning [this message]
2021-02-05 14:28   ` vincent Dupaquis
2021-02-05 14:34     ` Jan Vrany
2021-02-05 14:51       ` vincent Dupaquis

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=54B2CC51-8AA2-43AE-95F6-80F5B4BA8128@comcast.net \
    --to=paulkoning@comcast.net \
    --cc=gdb@sourceware.org \
    --cc=v.dupaquis@trusted-objects.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).