From: Dmitry Antipov <dmantipov@yandex.ru>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: --enable-gcc-warnings is broken on Fedora 21 by GnuTLS code
Date: Wed, 24 Dec 2014 10:07:56 +0300 [thread overview]
Message-ID: <549A664C.4040908@yandex.ru> (raw)
In-Reply-To: <5499DDEA.4070005@cs.ucla.edu>
On 12/24/2014 12:26 AM, Paul Eggert wrote:
> I guess I'm not fully understanding the problem they're trying to fix.
IIUC the problem is:
1) On ELF/GCC-compatible systems, GnuTLS author(s) wants to initialize the library
with gnutls_global_init called from __attribute__((constructor)) function.
Since gnutls_global_init uses memory allocation functions, any call to
gnutls_global_set_mem_functions from an application is just too late.
2) Emacs' GnuTLS code doesn't care about GNUTLS_E_MEMORY_ERROR too much because
we assume that the library can call our xmalloc and friends, where we actually
handle errors in Emacs-specific way.
IMO the best approach is to review/fix src/gnutls.c to handle GNUTLS_E_MEMORY_ERROR
among other errors and don't interfere in the library itself in any way.
Dmitry
next prev parent reply other threads:[~2014-12-24 7:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 8:38 --enable-gcc-warnings is broken on Fedora 21 by GnuTLS code Dmitry Antipov
2014-12-12 9:07 ` Eli Zaretskii
2014-12-12 9:26 ` Paul Eggert
2014-12-23 10:52 ` Dmitry Antipov
2014-12-23 18:28 ` Eli Zaretskii
2014-12-23 21:26 ` Paul Eggert
2014-12-24 7:07 ` Dmitry Antipov [this message]
2014-12-26 0:19 ` Paul Eggert
2014-12-26 0:25 ` Lars Ingebrigtsen
2014-12-26 8:23 ` Eli Zaretskii
2014-12-26 17:38 ` Paul Eggert
2014-12-27 8:08 ` Eli Zaretskii
2014-12-28 8:38 ` Paul Eggert
2014-12-28 15:20 ` Eli Zaretskii
2014-12-12 9:09 ` Paul Eggert
2014-12-12 9:30 ` Eli Zaretskii
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=549A664C.4040908@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.