From: Michael Heerdegen <michael_heerdegen@web.de>
To: "Петров Андрей" <an.petrov@pay-lab.ru>
Cc: 52479@debbugs.gnu.org
Subject: bug#52479: 27.2; EDebugging stops when breakpoint condition can not be printed
Date: Wed, 15 Dec 2021 06:26:38 +0100 [thread overview]
Message-ID: <8735muxwtt.fsf@web.de> (raw)
In-Reply-To: <62d5f9445730439e9d6b765f3d181c78@pay-lab.ru> ("Петров Андрей"'s message of "Tue, 14 Dec 2021 13:03:51 +0000")
Петров Андрей <an.petrov@pay-lab.ru> writes:
> Hello, team!
Hello - thanks for your (very well done and pleasant to read!) report.
> Debugger entered--Lisp error: (error "Apparently circular structure being printed")
> apply(debug error (error "Apparently circular structure being printed"))
> edebug(error (error "Apparently circular structure being printed"))
> signal(error ("Apparently circular structure being printed"))
> edebug-signal(error ("Apparently circular structure being printed"))
> message("Break: %s => %s" filtered (#<field field-157aa078be4c>))
Another symptom of printing the wrong way, similar to bug#52222.
Printing with `edebug-safe-prin1-to-string' should fix it and be the
right thing, right?
> P.S. I could not copy the text from emacs with C-c M-i according to hint:
> While in the mail buffer:
> Type C-c C-c to send the bug report.
> Type C-x k RET to cancel (don’t send it).
> Type C-c M-i to copy text to your preferred mail program. <----
Hmm, that calls `report-emacs-bug-insert-to-mailer'. You have set up a
mailer on your system and it works all fine? If you think Emacs is not
behaving here, can you please create a separate report? - that this
works is very important. Maybe you can already give debugging a try?
Thanks,
Michael.
next prev parent reply other threads:[~2021-12-15 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 13:03 bug#52479: 27.2; EDebugging stops when breakpoint condition can not be printed Петров Андрей
2021-12-15 5:26 ` Michael Heerdegen [this message]
2021-12-15 7:01 ` Петров Андрей
2021-12-19 13:05 ` Lars Ingebrigtsen
2021-12-19 15:50 ` Michael Heerdegen
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=8735muxwtt.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=52479@debbugs.gnu.org \
--cc=an.petrov@pay-lab.ru \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.