unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Cochran <robert-emacs@cochranmail.com>
Cc: shanemhansen@gmail.com, 24041@debbugs.gnu.org
Subject: bug#24041: 25.1.50; xwidget + -nw mode gives segfault
Date: Mon, 22 Aug 2016 17:41:54 +0300	[thread overview]
Message-ID: <83k2f8c1cd.fsf@gnu.org> (raw)
In-Reply-To: <878tvpa6w6.fsf@cochranmail.com> (message from Robert Cochran on Sun, 21 Aug 2016 19:12:41 -0700)

> From: Robert Cochran <robert-emacs@cochranmail.com>
> Cc: Robert Cochran <robert-emacs@cochranmail.com>,  shanemhansen@gmail.com,  24041@debbugs.gnu.org
> Date: Sun, 21 Aug 2016 19:12:41 -0700
> 
> Anyways, I have a patch, below, that's my first stab at solving the
> problem. All it does is call `check_x_display_info` with the current
> frame and allows any resulting error signals to propagate back up.
> 
> Probably not the most elegant solution, but I'm not entirely clear what
> can and can't be done from within the Emacs C core. Suggestions are very
> welcome.

My only comment is that you could call check_x_display_info with Qnil
as its argument.

Otherwise, LGTM, thanks.  And I see nothing inelegant in this patch.





  reply	other threads:[~2016-08-22 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 16:04 bug#24041: 25.1.50; xwidget + -nw mode gives segfault Shane Hansen
2016-08-19 18:36 ` Robert Cochran
2016-08-20  7:32   ` Eli Zaretskii
2016-08-20 21:33     ` Robert Cochran
2016-08-21  2:40       ` Eli Zaretskii
2016-08-22  2:12         ` Robert Cochran
2016-08-22 14:41           ` Eli Zaretskii [this message]
2016-08-22 18:30             ` Robert Cochran
2016-08-22 18:49               ` Eli Zaretskii
2016-08-22 19:52                 ` joakim
2016-08-22 20:28                   ` Robert Cochran
2016-08-23  2:40                     ` Eli Zaretskii
2019-08-28 20:04 ` Lars Ingebrigtsen
2019-08-29 11:00   ` Robert Pluim

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=83k2f8c1cd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24041@debbugs.gnu.org \
    --cc=robert-emacs@cochranmail.com \
    --cc=shanemhansen@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).