all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Antipov <dmantipov@yandex.ru>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 18410@debbugs.gnu.org
Subject: bug#18410: Use SAFE_ALLOCA etc. to avoid unbounded stack allocation.
Date: Fri, 05 Sep 2014 12:59:27 +0400	[thread overview]
Message-ID: <54097B6F.8000306@yandex.ru> (raw)
In-Reply-To: <5409536B.5090201@cs.ucla.edu>

On 09/05/2014 10:08 AM, Paul Eggert wrote:

> Attached is a patch to fix the unbounded alloca calls that I found when auditing the Emacs source.
> I'm sending this to bug-gnu-emacs to give Eli a heads-up, as some of the fixes affect Windows code.
> This patch is relative to Emacs trunk bzr 117822.

If __GNUC__, can't we use __attribute__ ((cleanup (freeing_function))) for implicit calls
to SAFE_FREE, similar to destructors in C++?

Dmitry






  parent reply	other threads:[~2014-09-05  8:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05  6:08 bug#18410: Use SAFE_ALLOCA etc. to avoid unbounded stack allocation Paul Eggert
2014-09-05  8:45 ` Dmitry Antipov
2014-09-05 15:01   ` Paul Eggert
2014-09-05 15:44   ` Stefan Monnier
2014-09-05 16:04     ` Andreas Schwab
2014-09-05 17:22       ` Stefan Monnier
2014-09-05  8:59 ` Dmitry Antipov [this message]
2014-09-05 15:03   ` Paul Eggert
2014-09-07  7:20 ` Paul Eggert
2014-09-07 17:09   ` Eli Zaretskii
2014-09-07 20:33     ` Paul Eggert
2014-09-08  2:22       ` Stefan Monnier
2014-09-08  2:35         ` Eli Zaretskii
2014-09-08  2:43           ` Stefan Monnier
2014-09-08  2:38         ` Paul Eggert
2014-09-08  3:17           ` Demetrios Obenour
2014-09-08  3:19             ` Daniel Colascione
2014-09-08  3:20               ` Demetrios Obenour
2014-09-08  7:26           ` Dmitry Antipov
2014-09-08  2:36       ` Eli Zaretskii
2014-09-08 12:48         ` Stefan Monnier
2014-09-09 13:17           ` Eli Zaretskii
2014-09-09 13:49             ` Stefan Monnier

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=54097B6F.8000306@yandex.ru \
    --to=dmantipov@yandex.ru \
    --cc=18410@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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.