X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Tue, 8 Feb 2011 13:24:48 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: TP_NUM_C_BUFS too small
Message-ID: <20110208122448.GL24247@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <AANLkTinS8oPJqwsoYkCkkuYvFY5rQTKgiP4nJEhEA0J6 AT mail DOT gmail DOT com> <20110208115915 DOT GK24247 AT calimero DOT vinschen DOT de> <AANLkTi=1Com2uXWddcUnF32g5bnJRB6Rzc1HBQGFMG5z AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <AANLkTi=1Com2uXWddcUnF32g5bnJRB6Rzc1HBQGFMG5z@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Feb  8 13:14, marco atzeri wrote:
> On Tue, Feb 8, 2011 at 12:59 PM, Corinna Vinschen  wrote:
> > On Feb  7 22:38, marco atzeri wrote:
> >> Suggestion for debugging ?
> >
> > Build the Cygwin DLL for debugging (just -g, no -O2), build octave for
> > debugging, and try to find the problem.
> >
> > What I can see from the stack dump is that it happens when trying to
> > open a file.  If you find the Cygwin call (probably, but not necessarily
> > open()) from octave in which the problem is encountered, you can narrow
> > down the problem to somewhere between this call and the previous
> > file-related call since all of these calls access the TLS buffers.  From
> > there it's detective work.  Maybe a watchpoint on the aforementioned
> > counter helps (class tls_pathbuf, member c_cnt).
> >
> > This is pretty tricky to find, I fear.
> 
> Time to learn serious gdb debugging.

There's some chance that this is a Cygwin bug.  If you can narrow down
the problem to a specific code snippet in octave, you may be able to
extract a very simple testcase in plain C which allows to reproduce the
problem without the zillions of octave/fltk code lines.  That would be
most helpful in case it is a Cygwin problem.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple