From: Ross Biro <ross.biro@mindspring.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 13479@debbugs.gnu.org
Subject: bug#13479: Cross Compiling for ARM
Date: Fri, 18 Jan 2013 17:09:36 -0500 [thread overview]
Message-ID: <CAJ56fyiL62MtXUqD5PygCF3KUs-kJ5vmQ7S8bcBvn=fq21uMXg@mail.gmail.com> (raw)
In-Reply-To: <50F98C7B.8090708@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
I haven't investigated. But because protecting those calls by if
(initialized) and even moving the lisp->C binding for
window_root_window_resize_vertically to after initialization didn't help, I
suspect the issue might be deeper than just protecting C calls to lisp. I
really don't know how to follow up though.
Ross
On Fri, Jan 18, 2013 at 12:55 PM, martin rudalics <rudalics@gmx.at> wrote:
> > Most/all calls to Elisp from C should protect themselves with calls to
> > Ffboundp or similar, indeed. Martin, could you take care of that?
>
> I'm not sure. If most/all calls should be protected we'd better provide
> call_[1-4]_safe function for this purpose. But I haven't the slightest
> idea of what might happen when some of these functions don't get called.
>
> martin
>
[-- Attachment #2: Type: text/html, Size: 1260 bytes --]
next prev parent reply other threads:[~2013-01-18 22:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 19:36 bug#13479: Cross Compiling for ARM Ross Biro
2013-01-18 14:26 ` Stefan Monnier
2013-01-18 17:55 ` martin rudalics
2013-01-18 22:09 ` Ross Biro [this message]
2013-01-19 10:11 ` martin rudalics
2013-01-23 3:49 ` Ross Biro
2013-01-23 7:31 ` martin rudalics
2013-01-19 1:18 ` Stefan Monnier
2013-01-24 4:42 ` Jason Rumney
2024-01-10 11:11 ` Stefan Kangas
-- strict thread matches above, loose matches on Subject: below --
2011-07-28 18:53 bug#9192: Cross-compile " Toon Claes
2024-01-10 11:11 ` bug#13479: Cross Compiling " Stefan Kangas
2024-01-10 11:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 11:56 ` Stefan Kangas
2024-01-10 13:10 ` Toon Claes via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CAJ56fyiL62MtXUqD5PygCF3KUs-kJ5vmQ7S8bcBvn=fq21uMXg@mail.gmail.com' \
--to=ross.biro@mindspring.com \
--cc=13479@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).