public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: archer@sourceware.org
Subject: Re: archer/tromey patches left to merge
Date: Mon, 14 Oct 2013 19:27:00 -0000	[thread overview]
Message-ID: <525C4584.1030202@redhat.com> (raw)
In-Reply-To: <87siw33ol6.fsf@fleche.redhat.com>

On 14/10/13 15:37, Tom Tromey wrote:
> Phil> * gdb.cli() command.
> [...]

Thanks for the reply Tom.  Here is my plan, pending other comments.

* Merge caller_is and caller_matches functions.

  I will keep them as two separate functions.  My first thought was to
  achieve the results of both with optional keyword arguments, but
  after investigating a little this would probably end up with a
  function heavily loaded with conditional keyword arguments.  It
  removes simplicity and adds complexity, so going with how it stands
  now.  I will add the option to search the entire stack.  I will need
  to write tests and documentation for both.

* Merge -P and gdb.cli()

  These two patches will be merged as one submission as they seem to
  be complimentary in a use-case sense.  I will need to write tests
  and documentation for both.  The -P tests and the gdb.cli() tests
  seem to be non-trivial in the GDB test suite.

* Merge ignore_errors command.

  Tom provided a case that it is needed.  Needs tests and
  documentation.

* Merge in_scope function.

  I think this is useful, so I will port it.  Needs test and
  documentation.  (As an aside, I am not sure where we should document
  these python only functions.  Will discuss.)

* Merge pahole command.

  I am not sure how to make this language agnostic, or even how to
  make it complimentary with ptype.  (We will discuss this more when
  the time-slot arrives in my schedule to consider the effort of
  porting it).
  
That's the order I intend to work on them as time allows.  Lastly, I
will delete the defunct code orphans and remove the obsoleted commands
from the branch.

Cheers,

Phil

  reply	other threads:[~2013-10-14 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 11:26 Phil Muldoon
2013-10-14 14:38 ` Tom Tromey
2013-10-14 19:27   ` Phil Muldoon [this message]
2013-10-14 19:31     ` Tom Tromey

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=525C4584.1030202@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=archer@sourceware.org \
    --cc=tromey@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).