Re: reproducible cygwin memory problems

2006-08-20 Thread emacs user
ok, let me try again. here is a case in which I try to run latest cvs gnu emacs under gdb and this just immediately freezes x windows. surely someone in the cygwin/ emacs teams would be interested in figuring this out...? ~ $ startx [1] 304 ~ $ Welcome to the XWin X Server Vendor: The

Re: reproducible cygwin memory problems

2006-08-18 Thread Eli Zaretskii
Date: Mon, 14 Aug 2006 08:58:12 +0200 From: Corinna Vinschen [EMAIL PROTECTED] As far as I could tell from the OP's report about Emacs configuration results, available here: http://www.deas.harvard.edu/climate/eli/emacs-debug/ Emacs he built does not use mmap. Here's the

Re: reproducible cygwin memory problems

2006-08-18 Thread Corinna Vinschen
On Aug 18 14:40, Eli Zaretskii wrote: From: Corinna Vinschen [EMAIL PROTECTED] There is no known issue. The heap is an area of reserved memory, which is on demand commited when sbrk is called. If the heap is too small to fit the new allocation, more memory is reserved/commited. When

Re: reproducible cygwin memory problems

2006-08-14 Thread Eli Zaretskii
From: emacs user [EMAIL PROTECTED] Cc: cygwin@cygwin.com, emacs-pretest-bug@gnu.org, [EMAIL PROTECTED] Bcc: Date: Mon, 14 Aug 2006 08:11:25 -0400 well, as you probably remember one cannot run cvs emacs in gdb as this immediately crashes x windows in cygwin. No, I didn't remember. Why

Re: reproducible cygwin memory problems

2006-08-14 Thread Corinna Vinschen
On Aug 13 22:11, Eli Zaretskii wrote: Date: Sun, 13 Aug 2006 11:23:16 +0200 From: Reini Urban [EMAIL PROTECTED] Corinna Vinschen schrieb: ... Ok, back to mmap/munmap. Private anonymous mappings are implemented in Cygwin by calling VirtualAlloc/VirtualFree. However, due to

Re: reproducible cygwin memory problems

2006-08-14 Thread Corinna Vinschen
On Aug 13 11:23, Reini Urban wrote: Corinna Vinschen schrieb: ... Ok, back to mmap/munmap. Private anonymous mappings are implemented in Cygwin by calling VirtualAlloc/VirtualFree. However, due to restrictions in the Win32 API, VirtualFree is only called by munmap, as soon as *all* pages

Re: reproducible cygwin memory problems

2006-08-14 Thread Corinna Vinschen
[Sorry, I forgot all the CCs] On Aug 13 22:11, Eli Zaretskii wrote: Date: Sun, 13 Aug 2006 11:23:16 +0200 From: Reini Urban [EMAIL PROTECTED] Corinna Vinschen schrieb: ... Ok, back to mmap/munmap. Private anonymous mappings are implemented in Cygwin by calling

Re: reproducible cygwin memory problems

2006-08-14 Thread emacs user
could you please write which .c files and which routines should I be looking at slightly more specifically? thanks... These are library functions, so no .c files are involved. Just (gdb) break sbrk (gdb) break mmap then visit text and image files as suggested and see which of these

Re: reproducible cygwin memory problems

2006-08-13 Thread Reini Urban
Corinna Vinschen schrieb: ... Ok, back to mmap/munmap. Private anonymous mappings are implemented in Cygwin by calling VirtualAlloc/VirtualFree. However, due to restrictions in the Win32 API, VirtualFree is only called by munmap, as soon as *all* pages within a single mmap'ed area are free'ed

Re: reproducible cygwin memory problems

2006-08-13 Thread Eli Zaretskii
Date: Sun, 13 Aug 2006 11:23:16 +0200 From: Reini Urban [EMAIL PROTECTED] Corinna Vinschen schrieb: ... Ok, back to mmap/munmap. Private anonymous mappings are implemented in Cygwin by calling VirtualAlloc/VirtualFree. However, due to restrictions in the Win32 API, VirtualFree is

Re: reproducible cygwin memory problems

2006-08-13 Thread emacs user
From: Eli Zaretskii [EMAIL PROTECTED] If I don't miss anything, it remains to be explained why the OP didn't see problems with normal buffers. Could the OP please try visiting several large text files, then kill their buffers, invoke the `garbage-collect' function (M-x garbage-collect RET),

Re: reproducible cygwin memory problems

2006-08-13 Thread Eli Zaretskii
From: emacs user [EMAIL PROTECTED] Bcc: Date: Sun, 13 Aug 2006 17:32:38 -0400 From: Eli Zaretskii [EMAIL PROTECTED] If I don't miss anything, it remains to be explained why the OP didn't see problems with normal buffers. Could the OP please try visiting several large text files, then

Re: reproducible cygwin memory problems

2006-08-12 Thread Reini Urban
emacs user schrieb: Dear cygwin friends, while debugging some emacs related problem, we seem to come to the conclusion that there is a cygwin issue here. can someone please comment on this? From: Eli Zaretskii [EMAIL PROTECTED] From: emacs user [EMAIL PROTECTED] Cc:

Re: reproducible cygwin memory problems

2006-08-12 Thread emacs user
Eli, here is a response from the cygwin list. thanks to Reini Urban for this. Date: Sat, 12 Aug 2006 11:32:01 +0200 From: Reini Urban rurban at x-ray dot at To: cygwin at cygwin dot com Subject: Re: reproducible cygwin memory problems Sender: cygwin-owner at cygwin dot com emacs user

Re: reproducible cygwin memory problems

2006-08-12 Thread emacs user
From: Eli Zaretskii [EMAIL PROTECTED] [I'm not subscribed to the Cygwin list, so please CC me directly.] From: emacs user [EMAIL PROTECTED] Bcc: Date: Sat, 12 Aug 2006 07:46:33 -0400 Cc: cygwin@cygwin.com Eli, here is a response from the cygwin list. thanks to Reini Urban for this.

Re: reproducible cygwin memory problems

2006-08-12 Thread Corinna Vinschen
On Aug 12 17:52, Eli Zaretskii wrote: It's possible that I'm wrong, of course. Let me state the facts and observations that led me to my conclusion: . The OP reported that the problem happens only with image files. When he edits text files, the Emacs memory footprint stays at a

Re: reproducible cygwin memory problems

2006-08-12 Thread Eli Zaretskii
[I'm not subscribed to the Cygwin list, so please CC me directly.] From: emacs user [EMAIL PROTECTED] Bcc: Date: Sat, 12 Aug 2006 07:46:33 -0400 Cc: cygwin@cygwin.com Eli, here is a response from the cygwin list. thanks to Reini Urban for this. Look Eli, that's really a bold

Re: reproducible cygwin memory problems

2006-08-11 Thread emacs user
Dear cygwin friends, while debugging some emacs related problem, we seem to come to the conclusion that there is a cygwin issue here. can someone please comment on this? From: Eli Zaretskii [EMAIL PROTECTED] From: emacs user [EMAIL PROTECTED] Cc: emacs-pretest-bug@gnu.org Bcc: Date: