From: Eli Zaretskii <eliz@gnu.org>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: 11236@debbugs.gnu.org
Subject: bug#11236: 24.1.50; Maximum buffer size exceeded
Date: Mon, 16 Apr 2012 19:54:16 +0300 [thread overview]
Message-ID: <83ehrnsjlz.fsf@gnu.org> (raw)
In-Reply-To: <DB60B4EC-EB35-4F10-8E61-A80D80E4B80A@Freenet.DE>
> Cc: 11236@debbugs.gnu.org
> From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
> Date: Mon, 16 Apr 2012 16:59:47 +0200
>
>
> Am 14.04.2012 um 13:31 schrieb Eli Zaretskii:
>
> > It could be a compiler bug, but to
> > make sure it isn't an Emacs bug, I would suggest to look at the
> > machine code emitted by the compiler in an optimized build at the
> > point of the fatal error.
>
> I decided to perform something I understand: I modified the function
> buffer_overflow () to report where it was called. It happens in src/
> fileio.c on line #3424, so buf_growth_max < likely_growth is true.
Can you show all the other variables involved in the calculations
leading to line 3424 of fileio.c?
next prev parent reply other threads:[~2012-04-16 16:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 14:04 bug#11236: 24.1.50; Maximum buffer size exceeded Peter Dyballa
2012-04-13 15:31 ` Eli Zaretskii
2012-04-14 10:57 ` Peter Dyballa
2012-04-14 11:31 ` Eli Zaretskii
2012-04-16 14:59 ` Peter Dyballa
2012-04-16 16:54 ` Eli Zaretskii [this message]
2012-04-16 20:12 ` Peter Dyballa
2012-04-16 20:39 ` Andreas Schwab
2012-04-16 22:09 ` Peter Dyballa
2012-04-14 15:27 ` Peter Dyballa
2012-04-15 12:02 ` Peter Dyballa
2012-04-15 22:44 ` Peter Dyballa
2012-04-15 23:48 ` Glenn Morris
2012-04-16 9:03 ` Peter Dyballa
2012-04-16 10:28 ` Andreas Schwab
2012-04-16 13:59 ` Peter Dyballa
2012-04-16 18:24 ` Glenn Morris
2012-04-16 20:16 ` Peter Dyballa
2012-04-23 9:37 ` Andreas Schwab
2012-04-23 5:12 ` Paul Eggert
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=83ehrnsjlz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11236@debbugs.gnu.org \
--cc=Peter_Dyballa@Freenet.DE \
/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.