From: Phil Muldoon <pmuldoon@redhat.com>
To: archer@sourceware.org
Subject: Re: [patch] Fix RH BZ 672235
Date: Thu, 27 Jan 2011 10:47:00 -0000 [thread overview]
Message-ID: <m3pqri8vyp.fsf@redhat.com> (raw)
In-Reply-To: <m339ofo1v2.fsf@redhat.com> (Phil Muldoon's message of "Wed, 26 Jan 2011 20:18:25 +0000")
Phil Muldoon <pmuldoon@redhat.com> writes:
> Bug:
>
> http://bugzilla.redhat.com/show_bug.cgi?id=672235
>
> The latter half of this bug was caused by removing the value function
> from gdb.Symbol. This happened quite some time ago, so I am a little
> surprised it took this long to surface.
I should have read Tom's email about reworking backtraces before I
hacked on this. As FrameWrapper, et al is being redesigned (see Tom's
patch), I'm not sure we should submit the gdb.Symbol.block() upstream
API upstream now.
This patch might be enough to allow new-backtrace to continue working in
Fedora (via an rpm patch) until the new functionality is written and
implemented. WDYT?
Cheers
Phil
prev parent reply other threads:[~2011-01-27 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 20:18 Phil Muldoon
2011-01-27 10:47 ` Phil Muldoon [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=m3pqri8vyp.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).