From: Steve Revilak <steve@srevilak.net>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: 5333@debbugs.gnu.org
Subject: bug#5333: 23.1.91; NextStep/Mac OS X: emacs -nw crash in input_available_signal + 67 (keyboard.c:7514)
Date: Tue, 12 Jan 2010 21:00:35 -0500 [thread overview]
Message-ID: <20100113020035.GB386@srevilak.net> (raw)
In-Reply-To: <20100109025209.GB406@srevilak.net>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
>> According to the stack trace, the crash seems to happen by
>> dereferencing NULL pointer (with some offset) in a non-main thread
>> executing the following code in the SIGIO handler.
>>
>> if (input_available_clear_time)
>> EMACS_SET_SECS_USECS (*input_available_clear_time, 0, 0);
>>
>> EMACS_SET_SECS_USECS consists of multiple instructions, and
>> input_available_clear_time might be cleared to NULL by the main thread
>> between the NULL-check and the completion of EMACS_SET_SECS_USECS in a
>> non-main thread.
>>
>> Could you try the following patch for a while to see if it can avoid
>> the issue?
> YAMAMOTO,
>
> Thank you for the patch. I'll will test it this week.
I've been using YAMAMOTO's patch for two days, and no crashes. Yay!
If I do not see a crash by Friday, then I will close bug#5333.
Steve
[-- Attachment #2: Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2010-01-13 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 15:09 bug#5333: 23.1.91; NextStep/Mac OS X: emacs -nw crash in input_available_signal + 67 (keyboard.c:7514) steve
2010-01-09 1:54 ` YAMAMOTO Mitsuharu
2010-01-09 2:52 ` Steve Revilak
2010-01-13 2:00 ` Steve Revilak [this message]
2010-01-13 5:00 ` YAMAMOTO Mitsuharu
2010-01-13 5:01 ` bug#5333: marked as done (23.1.91; NextStep/Mac OS X: emacs -nw crash in input_available_signal + 67 (keyboard.c:7514)) Emacs bug Tracking System
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=20100113020035.GB386@srevilak.net \
--to=steve@srevilak.net \
--cc=5333@debbugs.gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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.