X-Spam-Check-By: sourceware.org Message-ID: X-Sender: emacs_user@hotmail.com In-Reply-To: From: "emacs user" To: eliz@gnu.org Cc: cygwin@cygwin.com, emacs-pretest-bug@gnu.org, hack@robf.de Subject: Re: reproducible cygwin memory problems Date: Mon, 14 Aug 2006 08:11:25 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk 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 > > 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 >breakpoint actually breaks. well, as you probably remember one cannot run cvs emacs in gdb as this immediately crashes x windows in cygwin. I do wish there would be someone more knowledgeble then me doing the testing with cygwin, now that we've made some progress. I am worried that I may be missing something elementary and waisting your time. installing cygwin and then cvs gnu emacs would take a few minutes only... anyway, am happy to keep trying. _________________________________________________________________ Don’t just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ -- 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/