From: Joel Brobecker <brobecker@adacore.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, Doug Evans <dje@google.com>,
gdb-patches <gdb-patches@sourceware.org>,
arnez@vnet.linux.ibm.com
Subject: Re: GDB 7.9 release update
Date: Thu, 05 Feb 2015 05:55:00 -0000 [thread overview]
Message-ID: <20150205055541.GD4738@adacore.com> (raw)
In-Reply-To: <54D1C3E6.5030109@redhat.com>
> Sorry for the delay. I've just come back from some meetings and then
> FOSDEM. I'll get to work on this bug. But again I do not consider it
> a blocker, certainly not for release. There are workarounds for it
> (disable frame-filter all), for the cases of exceptionally long
> backtraces.
>
> It is unfortunately a non trivial issue having to do with both Python
> interrupts and GDB exceptions, so a fix has to be carefully tested.
Thanks for the update, Phil. Since this is non-trivial, and
therefore potentially risky for the branch, let's put that one
into the "Maybe" category.
Let's re-eval the state of the branch again on Wed (Feb 12th).
--
Joel
next prev parent reply other threads:[~2015-02-05 5:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 11:17 Joel Brobecker
2015-01-28 14:32 ` Doug Evans
2015-01-29 7:19 ` Joel Brobecker
2015-02-03 14:24 ` Pedro Alves
2015-02-03 18:45 ` Eli Zaretskii
2015-02-04 4:11 ` Joel Brobecker
2015-02-04 7:02 ` Phil Muldoon
2015-02-05 5:55 ` Joel Brobecker [this message]
2015-02-17 10:34 ` ready GDB 7.9 release? (was: "Re: GDB 7.9 release update") Joel Brobecker
2015-02-17 11:15 ` ready GDB 7.9 release? Pedro Alves
2015-02-17 11:21 ` Joel Brobecker
2015-02-17 12:02 ` Pedro Alves
2015-01-29 16:28 ` GDB 7.9 release update Andreas Arnez
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=20150205055541.GD4738@adacore.com \
--to=brobecker@adacore.com \
--cc=arnez@vnet.linux.ibm.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=pmuldoon@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).