public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Pete McCann <mccap@lucent.com>
To: cygwin@cygwin.com
Subject: Re: SEGV in conv_path_list_buf_size with xemacs-21.5-b13 and cygwin-snapshot-20030904-1
Date: Fri, 12 Sep 2003 19:42:00 -0000	[thread overview]
Message-ID: <16226.8585.30792.371032@gargle.gargle.HOWL> (raw)
In-Reply-To: <20030910085841.GA1859@cygbert.vinschen.de>


Corinna Vinschen writes:

> On Tue, Sep 09, 2003 at 03:33:42PM -0500, Pete McCann wrote:
> > 
> > Hi,
> > 
> > After some more hunting, I now understand there is a difference
> > between the cygwin heap and the user heap.  My problem is that I'm
> > running out of cygwin heap:
> 
> Can you check how often the function cygwin_posix_to_win32_path_list_buf_size()
> is called?  Does that happen fairly often?
> 
> Corinna

That function is called about 600 - 700 times (sometimes as many as
2000-3000) when I do a simple operation like checking for new mail in
the spool file.  cygheap_max grows steadily with each call.

-Pete



--
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/

  parent reply	other threads:[~2003-09-12 19:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 19:21 SEGV in conv_path_list_buf_size with xemacs-21.5-b13 and cygwin-1.3.22-1 Pete McCann
2003-06-03 22:00 ` Christopher Faylor
2003-06-04 22:03   ` Pete McCann
2003-06-04 23:01     ` Christopher Faylor
2003-06-05 19:26       ` Pete McCann
2003-06-05 19:42         ` Christopher Faylor
2003-09-04 16:14           ` Pete McCann
2003-09-09 20:33             ` SEGV in conv_path_list_buf_size with xemacs-21.5-b13 and cygwin-snapshot-20030904-1 Pete McCann
2003-09-10  8:58               ` Corinna Vinschen
2003-09-12 19:42               ` Pete McCann [this message]
2003-09-12 21:23                 ` Pete McCann
2003-09-13  8:44                   ` Corinna Vinschen

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=16226.8585.30792.371032@gargle.gargle.HOWL \
    --to=mccap@lucent.com \
    --cc=cygwin@cygwin.com \
    /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.
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).