From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: j.e.widen@gmail.com, 65445@debbugs.gnu.org
Subject: bug#65445: 29.1; Android emacs: False memory full condition, due to Java exception (?)
Date: Tue, 22 Aug 2023 10:27:59 +0800 [thread overview]
Message-ID: <87bkezak0g.fsf@yahoo.com> (raw)
In-Reply-To: <83o7izu802.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 22 Aug 2023 05:27:09 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: 65445@debbugs.gnu.org
>> Date: Tue, 22 Aug 2023 07:52:18 +0800
>> From: Po Lu via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> When an exception is registered by android_exception_check, it makes an
>> attempt to print it to the log buffer. Piping it to `grep -A10
>> "Possible out of memory error"' should uncover the Java stack trace
>> saved in the exception.
>
> Would it be useful to add this to etc/DEBUG?
Yes, I will do that.
next prev parent reply other threads:[~2023-08-22 2:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 20:46 bug#65445: 29.1; Android emacs: False memory full condition, due to Java exception (?) Johan Widén
2023-08-21 23:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-22 2:27 ` Eli Zaretskii
2023-08-22 2:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-22 5:21 ` Johan Widén
2023-08-22 5:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-22 5:52 ` Johan Widén
2023-08-22 6:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-22 7:09 ` Johan Widén
2023-08-22 7:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 16:30 ` Stefan Kangas
2023-09-02 17:21 ` Johan Widén
2023-09-02 18:52 ` Stefan Kangas
2023-09-02 18:56 ` Johan Widén
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=87bkezak0g.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=65445@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=j.e.widen@gmail.com \
--cc=luangruo@yahoo.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.
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).