From: Po Lu <luangruo@yahoo.com>
To: "andrés ramírez" <rrandresf@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: help needed for getting a backtrace ( multi-head emacs_abort on lucid-frame)
Date: Tue, 19 Apr 2022 08:53:57 +0800 [thread overview]
Message-ID: <87sfq9hp0a.fsf@yahoo.com> (raw)
In-Reply-To: <868rs2h4u6.fsf@gmail.com> ("andrés ramírez"'s message of "Mon, 18 Apr 2022 13:57:21 +0000")
andrés ramírez <rrandresf@gmail.com> writes:
> Hi. Po Lu.
>
>>>>>> "Po" == Po Lu <luangruo@yahoo.com> writes:
>
>
> [...]
>
>
> Po> What about this?
>
> This patch also does NOT fix it.
>
> But I have noticed inside x_error_quiter there is a message about
> ignoring BadName errors.
>
> Could this kind of X error be ignored safely also?.
No. It will interfere with handlers set by other programs.
x_catch_errors should catch the error before it is propagated to
x_error_quitter. I wonder why it isn't working.
I will look into this some more, thanks.
next prev parent reply other threads:[~2022-04-19 0:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 21:05 help needed for getting a backtrace ( multi-head emacs_abort on lucid-frame) Andrés Ramírez
2022-04-17 23:59 ` Po Lu
[not found] ` <87y203np3y.fsf@manco.pe>
[not found] ` <87v8v7kv9h.fsf@yahoo.com>
2022-04-18 3:52 ` andrés ramírez
2022-04-18 5:06 ` Po Lu
2022-04-18 5:40 ` andrés ramírez
2022-04-18 5:55 ` Po Lu
2022-04-18 6:16 ` andres.ramirez
2022-04-18 6:53 ` Po Lu
2022-04-18 7:37 ` andrés ramírez
2022-04-18 8:00 ` Po Lu
2022-04-18 8:14 ` andrés ramírez
2022-04-18 8:34 ` Po Lu
2022-04-18 8:49 ` andrés ramírez
2022-04-18 9:05 ` Po Lu
2022-04-18 9:32 ` andrés ramírez
2022-04-18 10:29 ` Po Lu
2022-04-18 13:57 ` andrés ramírez
2022-04-19 0:53 ` Po Lu [this message]
2022-04-19 20:44 ` andrés ramírez
2022-04-18 14:43 ` multi-head x error RenderBadGlyph on lucid-frame (was: help needed with backtrace ) andrés ramírez
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=87sfq9hp0a.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=rrandresf@gmail.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 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.