From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Suspicious error in GTk
Date: Mon, 11 Jun 2007 17:16:49 -0400 [thread overview]
Message-ID: <jwv4ple42n2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <871wgixm5k.fsf@stupidchicken.com> (Chong Yidong's message of "Mon\, 11 Jun 2007 16\:37\:43 -0400")
>> While trying out SYNC_INPUT with Gtk together with the `eassert' debugging
>> I bumped into the appended backtrace, right at startup. Basically, the code
>> run from XTread_socket (run asynchronously at any time) can call
>> update_frame_tool_bar which in turn calls xpm_load which ends up calling
>> encode_coding_string (to encode the file's name) which fiddles with
>> specpdl_ptr (via record_unwind_protect) and may run elisp code.
>>
>> Most likely it will usually not lead to any problem, but I believe it'll
>> bite every now and then and will be difficult to trace.
AFAICT my bug report has nothing to do with alloc.c. I even believe it's
got nothing to do with SYNC_INPUT. I just happened to bump into it with
a SYNC_INPUT build (because all my builds use SYNC_INPUT).
> ISTR that parts of alloc.c are carried out inside BLOCK_INPUT, but
> only if SYNC_INPUT is off.
This is an optimization: if SYNC_INPUT is used, we never use malloc inside
a signal handler, so we don't need to wrap them with BLOCK_INPUT.
> Does this mean that we need BLOCK_INPUT even when SYNC_INPUT is on?
I'm not sure what "this" refers to.
Stefan
next prev parent reply other threads:[~2007-06-11 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 20:19 Suspicious error in GTk Stefan Monnier
2007-06-11 20:37 ` Chong Yidong
2007-06-11 21:16 ` Stefan Monnier [this message]
2007-06-12 6:13 ` Jan Djärv
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=jwv4ple42n2.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
/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.