From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: TP_NUM_C_BUFS too small
Date: Tue, 08 Feb 2011 12:25:00 -0000 [thread overview]
Message-ID: <20110208122448.GL24247@calimero.vinschen.de> (raw)
In-Reply-To: <AANLkTi=1Com2uXWddcUnF32g5bnJRB6Rzc1HBQGFMG5z@mail.gmail.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
next prev parent reply other threads:[~2011-02-08 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 21:38 marco atzeri
2011-02-08 11:59 ` Corinna Vinschen
2011-02-08 12:14 ` marco atzeri
2011-02-08 12:25 ` Corinna Vinschen [this message]
2015-11-01 17:46 Helmut Karlowski
2015-11-01 19:35 ` Helmut Karlowski
2015-11-02 2:32 ` Mark Geisert
2015-11-02 11:15 ` Corinna Vinschen
2015-11-02 23:07 ` Helmut Karlowski
2015-11-03 13:02 ` 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=20110208122448.GL24247@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).