Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH, doc RFA] Add ability to set random attributes in python objfiles,progspaces
Date: Fri, 10 Oct 2014 17:21:00 -0000	[thread overview]
Message-ID: <21560.5551.568484.140907@ruffy2.mtv.corp.google.com> (raw)
In-Reply-To: <8338awbblf.fsf@gnu.org>

Eli Zaretskii writes:
 > Btw, why do we only support adding attributes for these 2 types of
 > objects?  Why not for any object?

Like most/all things in gdb/python, things get added by demand.


  reply	other threads:[~2014-10-10 17:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <yjt27g09qcx2.fsf@ruffy.mtv.corp.google.com>
2014-10-09 19:10 ` Doug Evans
2014-10-10  7:58 ` Eli Zaretskii
2014-10-10 17:21   ` Doug Evans [this message]
2014-10-10  8:00 ` Phil Muldoon
2014-10-10 17:35   ` Doug Evans
2014-10-10 18:25     ` Phil Muldoon
2014-10-17 20:29       ` Doug Evans
2014-10-18  5:40         ` Eli Zaretskii
2014-10-21 16:53           ` Doug Evans
2014-10-21 18:23             ` Phil Muldoon
2014-10-31  0:07               ` Doug Evans

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=21560.5551.568484.140907@ruffy2.mtv.corp.google.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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