X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <47432F5F.4080302@wustl.edu> <17393e3e0711201116v7c01c77by468aec648bf2d30a@mail.gmail.com> Subject: RE: Vim: segmentation fault Date: Tue, 20 Nov 2007 19:24:33 -0000 Message-ID: <05d101c82baa$fc8c7fc0$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <17393e3e0711201116v7c01c77by468aec648bf2d30a@mail.gmail.com> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id lAKJOnTf015383 On 20 November 2007 19:17, Matt Wozniski wrote: > And, there's no reason that should crash vim. Do you have the > 1.5 GB of memory that you'd need to open that file? Umm, you don't need that much memory to open a file, thanks to the wonders of file-backed virtual memory. But what you probably do need is a 1.5GB empty hole in your process address space (unless vim is intelligent enough to only mmap() part of the file at a time), and finding a hole that size is almost certainly impossible on 32-bit targets without enabling the boot.ini '/3GB' switch. However I don't know anything about the internals of vim, so can't be sure that's the cause. And it's certainly a bug that it doesn't fail gracefully. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/