Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <415ED93D.8050008@ateb.com>
Date: Sat, 02 Oct 2004 12:37:17 -0400
From: Reid Thompson <reid.thompson@ateb.com>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
MIME-Version: 1.0
To: Maarten Boekhold <boekhold@emirates.net.ae>
Cc: cygwin@cygwin.com
Subject: Re: Memory debugging under cygwin
References: <415E63AF.30403@emirates.net.ae>
In-Reply-To: <415E63AF.30403@emirates.net.ae>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

splint is available via setup also.
www.splint.org

Maarten Boekhold wrote:

> Hi all,
>
> I have a program that segfaults, and it's quite obvious that this is 
> caused due to some memory corruption. Except it segfaults at a place 
> where, if running it in gdb, there shouldn't be a problem. There seems 
> to be some memory corruption somewhere, and I can't figure out where.
>
> I tried linking the app with dmalloc, but I can't get it to generate a 
> log file, even if I explicitly request one by including calls to the 
> dmalloc library in the application. Valgrind doesn't seem to be 
> available on cygwin either.
>
> Can anybody recommend a way to debug this sort of error? Are there any 
> other memory debuggers available that work with cygwin?
>
> Maarten
>
> -- 
> 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/
>

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