From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: 24617@debbugs.gnu.org
Subject: bug#24617: 26.0.50; Handlers in `condition-case' should have programmatic access to the backtrace
Date: Thu, 29 Dec 2016 15:02:53 +0100 [thread overview]
Message-ID: <f31008ab-ac17-35ea-40aa-7f1a498ffc8f@gmail.com> (raw)
In-Reply-To: <m2zijf2jnn.fsf@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 621 bytes --]
On 12/29/2016 10:01 AM, Helmut Eller wrote:
>> Second, unconditionally copying the backtrace would be expensive
>>
>> Are you sure about that?
>
> No, but I would be surprised if it were cheap.
Collecting the textual backtrace (by calling 'backtrace') can take arbitrarily long, because it includes arguments, which can be large strings. I've run into this (99% of the time was spent on collecting backtraces).
Collecting a full backtrace with backtrace-frame (as objects) is quadratic, but I don't know if that matters. The master branch has mapbacktrace, which solves the quadratic part.
Clément.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-12-29 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 16:38 bug#24617: 26.0.50; Handlers in `condition-case' should have programmatic access to the backtrace Philipp Stephani
2016-10-04 19:41 ` Clément Pit--Claudel
2016-12-28 19:33 ` Philipp Stephani
2016-10-05 6:16 ` Helmut Eller
2016-12-28 20:08 ` Philipp Stephani
2016-12-29 9:01 ` Helmut Eller
2016-12-29 14:02 ` Clément Pit--Claudel [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f31008ab-ac17-35ea-40aa-7f1a498ffc8f@gmail.com \
--to=clement.pit@gmail.com \
--cc=24617@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).