unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mike Coleman <tutufan@gmail.com>
To: rms@gnu.org
Cc: 2790@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org
Subject: bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit GNU/Linux box
Date: Sat, 28 Mar 2009 11:27:57 -0500	[thread overview]
Message-ID: <3c6c07c20903280927k4b08ce52m3368a2ed6a9996f8@mail.gmail.com> (raw)
In-Reply-To: <E1LnaHt-00064L-ID@fencepost.gnu.org>

On Sat, Mar 28, 2009 at 10:17 AM, Richard M Stallman <rms@gnu.org> wrote:
>    The smallest file that produces the error has 536870912 bytes, exactly
>    512MB.  (This is via binary search, so assumes that there is just one
>    transition from "will" to "won't" as filesize increases.)
>
> It looks like you're simply hitting the limit on buffer size.
>
> But I suspect there is a bug here, because it sounds like
> you can visit a file whose size is bigger than most-positive-fixnum.
> If you do that, what value do you get for (point-max)?
> Is it negative?  I think it will be, and that we need
> to restrict the buffer size to be no more than most-positive-fixnum.

It appears to me that visiting a file larger than 512MB is simply
failing, with the given error message about the max buffer size.
(Note that 512MB is much, much smaller than most-positive-fixnum (==
2^64).)

So, to me, it seems like the behavior is "correct", if emacs only
promises to handle files as large as 512MB (on 64-bit platforms).

Nonetheless, I'd like it to handle much larger files.  Is there any
real reason not to just turn every (32-bit) "int" into a (64-bit)
"long" on 64-bit platforms?

Mike







  reply	other threads:[~2009-03-28 16:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 15:50 bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit Linux box Mike Coleman
2009-03-26 19:58 ` Eli Zaretskii
2009-03-26 21:01   ` Mike Coleman
2009-03-26 21:14     ` Eli Zaretskii
2009-03-26 21:33       ` Mike Coleman
2009-03-27  0:32         ` Stefan Monnier
2009-03-27  0:39           ` Mike Coleman
2009-03-27  3:08             ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit Linux Stefan Monnier
2009-03-27 16:29               ` Mike Coleman
2009-03-27  8:46         ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit Linux box Eli Zaretskii
2009-03-27 11:21       ` Andreas Schwab
2009-03-27  4:59 ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit GNU/Linux box Richard M Stallman
2009-03-27 16:27   ` Mike Coleman
2009-03-27 17:42     ` Eli Zaretskii
2009-03-28  2:12     ` Stefan Monnier
2009-03-28  5:24       ` Mike Coleman
2009-03-29 19:59         ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit Stefan Monnier
2009-03-28  8:45       ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit GNU/Linux box Eli Zaretskii
2009-03-28 11:12         ` Andreas Schwab
2009-03-28 12:03           ` Eli Zaretskii
2009-03-28 12:40             ` Andreas Schwab
2009-03-28 13:52               ` Eli Zaretskii
2009-03-29 20:13           ` Stefan Monnier
2009-03-29 20:10         ` Stefan Monnier
2009-03-29 20:44           ` Andreas Schwab
2009-03-30  0:59             ` Stefan Monnier
2009-03-30  8:08               ` Andreas Schwab
2009-03-30 13:01                 ` Stefan Monnier
2009-03-30 13:22                   ` Andreas Schwab
2009-03-29  2:15       ` Richard M Stallman
2009-03-29 20:14         ` Stefan Monnier
2009-03-28 15:17     ` Richard M Stallman
2009-03-28 16:27       ` Mike Coleman [this message]
     [not found]       ` <mailman.4163.1238258635.31690.bug-gnu-emacs@gnu.org>
2009-03-31 14:17         ` Ted Zlatanov
2011-09-11 22:10 ` bug#2790: emacs 22.1.1 cannot open 5GB file on 64GB 64-bit Linux box Lars Magne Ingebrigtsen
2011-09-12  2:59   ` 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

  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=3c6c07c20903280927k4b08ce52m3368a2ed6a9996f8@mail.gmail.com \
    --to=tutufan@gmail.com \
    --cc=2790@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=rms@gnu.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 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).