all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Dmitry Antipov <dmantipov@yandex.ru>,
	 Emacs development discussions <emacs-devel@gnu.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: --enable-gcc-warnings is broken on Fedora 21 by GnuTLS code
Date: Fri, 12 Dec 2014 01:09:21 -0800	[thread overview]
Message-ID: <548AB0C1.7090401@cs.ucla.edu> (raw)
In-Reply-To: <548AA97A.90404@yandex.ru>

Dmitry Antipov wrote:
> I'm just curious how to hook Emacs' xmalloc/xrealloc/xfree into GnuTLS without
> that.

Yes, without that it's not just that --enable-gcc-warnings is busted, it's that 
gnutls itself is busted when memory is low.

Apparently one is now supposed to do something like this:

gnutls_malloc = xmalloc;
gnutls_realloc = xrealloc;
gnutls_calloc = xcalloc;
gnutls_free = xfree;
gnutls_strdup = xstrdup;

although this does not appear to be documented.  What a pain.  Is that something 
you can test?  I don't have Fedora 21 installed yet.  (I think you'll have to 
define an xcalloc.)



  parent reply	other threads:[~2014-12-12  9:09 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
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 [this message]
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=548AB0C1.7090401@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=dmantipov@yandex.ru \
    --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.