public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Ray Ruvinskiy <rruvinsk@sybase.com>
Cc: archer@sourceware.org
Subject: Re: gdb.Parameter / backtrace.py in gdb 7.0?
Date: Fri, 04 Dec 2009 23:15:00 -0000	[thread overview]
Message-ID: <m38wdie3ft.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4B181B93.4030905@sybase.com> (Ray Ruvinskiy's message of "Thu, 03 Dec 2009 15:12:03 -0500")

>>>>> "Ray" == Ray Ruvinskiy <rruvinsk@sybase.com> writes:

Ray> I have noticed that the gdb repository is missing all of the Archer
Ray> python samples (i.e., backtrace.py and the rest of the stuff in
Ray> gdb.pythondir, including the attribute gdb.pythondir). I was hoping
Ray> that the scripts from the Archer branch would more or less just work
Ray> with gdb 7.0, but that appears not to be the case, as gdb.Parameter,
Ray> which backtrace.py uses, is completely missing from the gdb
Ray> repository. I've been trying to find out whether there is a reason for
Ray> all of this, but I can't find any e-mails anywhere.

There's no good reason, it is just that nobody has yet done the work to
merge things upstream.

This is something we plan to do, though it has been slow going.
Currently, Phil is the main person working on Python stuff, and he has
been focused on bug-fixing.

Ray> I was wondering what reason for the divergence is and whether there is
Ray> a version of filtering backtrace that works with gdb 7.0.

Nope.  Also, I think there is more missing than just Parameter.

Tom

  reply	other threads:[~2009-12-04 23:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 20:12 Ray Ruvinskiy
2009-12-04 23:15 ` Tom Tromey [this message]
2009-12-05  9:27   ` Phil Muldoon

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=m38wdie3ft.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=rruvinsk@sybase.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).