From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: dmantipov@yandex.ru, 16603@debbugs.gnu.org
Subject: bug#16603: 24.3.50; Segfault when viewing a backtrace
Date: Fri, 31 Jan 2014 10:37:21 +0200 [thread overview]
Message-ID: <838utw7dj2.fsf@gnu.org> (raw)
In-Reply-To: <87ha8klgeq.fsf@building.gnus.org>
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Dmitry Antipov <dmantipov@yandex.ru>, 16603@debbugs.gnu.org
> Date: Fri, 31 Jan 2014 00:11:25 -0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So either we should reserve some space for the debugger, or enlarge
> > max-specpdl-size before running the debugger, or refrain from running
> > the debugger in this specific case.
>
> Being able to run the debugger seems kinda nice. >"? So I think
> enlarging before running the debugger sounds like the right solution.
Yes, assuming we can make sure the debugger itself does not try to
traverse a circular structure. Also, we should disallow recursive
re-entering the debugger in this case. But perhaps there are already
facilities for that, I don't really know this area all that well.
next prev parent reply other threads:[~2014-01-31 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 2:20 bug#16603: 24.3.50; Segfault when viewing a backtrace Lars Ingebrigtsen
2014-01-31 7:03 ` Dmitry Antipov
2014-01-31 8:10 ` Eli Zaretskii
2014-01-31 8:11 ` Lars Ingebrigtsen
2014-01-31 8:37 ` Eli Zaretskii [this message]
2014-02-07 3:44 ` Lars Ingebrigtsen
2014-02-07 3:50 ` Lars Ingebrigtsen
2014-02-07 5:48 ` Dmitry Antipov
2014-02-08 1:23 ` Lars Ingebrigtsen
2014-02-10 6:26 ` Dmitry Antipov
2014-02-10 6:37 ` Lars Ingebrigtsen
2014-02-10 9:30 ` Dmitry Antipov
2014-02-10 9:32 ` Lars Ingebrigtsen
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=838utw7dj2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16603@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=larsi@gnus.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).