Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
To: cygwin AT cygwin DOT com
From: Larry Adams <larryjadams AT comcast DOT net>
Subject:  Re: Segfault in Cactid
Date: Sun, 11 Sep 2005 21:05:44 +0000 (UTC)
Lines: 48
Message-ID:  <loom.20050911T230301-535@post.gmane.org>
References:  <loom DOT 20050902T024037-588 AT post DOT gmane DOT org> <4317D378 DOT 236A02D9 AT dessent DOT net> <loom DOT 20050902T113935-922 AT post DOT gmane DOT org> <431835D4 DOT 6DD3EFE1 AT dessent DOT net>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes

Brian Dessent <brian <at> dessent.net> writes:

> 
> Larry Adams wrote:
> 
> > Brian, I am assuming that I can just download the latest cygwin of winsup 
and
> > then configure/make.  What configure/make options should I be using to
> > incorporate debug symbols?
> 
> <http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin>
> 
> The default compiler options include -g so you get symbols by default. 
> Note that in recent CVS versions this means a seperate .dbg file.
> 
> You can also add --enable-debugging to ./configure, but this enables a
> number of things in the code, not just compiler flags.  Grep for "#ifdef
> DEBUGGING" in the source for details.  Mostly this means more verbose
> strace ourput and some extra sanity checking.
> 
> > The previous version of Cactid did not have this problem.  The one major
> > change in this version of Cactid is that I am using upto 100 process 
threads
> > and each thread is allocating large amounts of memory using primarily
> > the "calloc" function.  I was wondering if maybe Cygwin is having 
difficulty
> > making memory available to the calloc function after several threads have
> > chopped up the heap.
> 
> Until you debug the crash it's all just speculation.  It could be a
> million things.  That said, even if the above was the case, Cygwin
> should not crap its pants and dereference a NULL pointer no matter how
> bad the heap is thrashed, so something is definitely wrong.
> 
> Brian
> 
> 

Brian,

I have applied the September 9th SNAPSHOT.  I noted that on the 5th and 6th of 
September the ChangeLog's sounded quite familiar.  I am currently running 2.5 
hours without issue.  Jury's still out, but one of the bug fixes was 
associated with attempting to close/free a NULL pointer. :)

Larry Adams
The Cacti Group



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