From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: 55672@debbugs.gnu.org
Subject: bug#55672: 29.0.50; Emacs crashes when calling start-process-shell-command xdg-open with process-connection-type set to nil
Date: Fri, 27 May 2022 17:57:21 +0800 [thread overview]
Message-ID: <87bkvjguwu.fsf@yahoo.com> (raw)
In-Reply-To: <87ilprs3vl.fsf@localhost> (Ihor Radchenko's message of "Fri, 27 May 2022 17:48:14 +0800")
Ihor Radchenko <yantar92@gmail.com> writes:
> However, I tried to play around with alternative ways to pass
> parameters. Using run -q -xrm '...' appears to work.
The problem is a process filter causing `x_clear_frame' to be called on
a frame whose GCs have not yet been realized. That should actually be
impossible.
Can you evaluate the following lines in that gdb session, and show the
output?
up 6
p *f->output_data.x
Thanks.
next prev parent reply other threads:[~2022-05-27 9:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 6:24 bug#55672: 29.0.50; Emacs crashes when calling start-process-shell-command xdg-open with process-connection-type set to nil Ihor Radchenko
2022-05-27 7:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 7:45 ` Ihor Radchenko
2022-05-27 7:49 ` Ihor Radchenko
2022-05-27 8:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 8:44 ` Ihor Radchenko
2022-05-27 9:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 9:15 ` Ihor Radchenko
2022-05-27 9:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 9:48 ` Ihor Radchenko
2022-05-27 9:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-05-27 10:04 ` Ihor Radchenko
2022-05-27 10:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 10:13 ` Ihor Radchenko
2022-05-27 10:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 10:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 10:35 ` Ihor Radchenko
2022-05-27 11:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 12:06 ` Ihor Radchenko
2022-05-27 13:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 13:37 ` Ihor Radchenko
2022-05-27 13:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-27 13:48 ` Ihor Radchenko
2022-07-24 5:48 ` Ihor Radchenko
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=87bkvjguwu.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=55672@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=yantar92@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 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).