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
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Segfault in Cactid
Date: Fri, 2 Sep 2005 11:11:17 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To:  <loom.20050902T113935-922@post.gmane.org>
Message-ID: <SERRANOWerOc0Ne0PaL0000007b@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Larry Adams
>Sent: 02 September 2005 10:48

> Brian Dessent <brian <at> dessent.net> writes:
> 
>> 
>> Larry Adams wrote:
>> 
>>> So my questions are: How do I trace the memory location above to a
>>> known system call using gdb?  When, I attach to my hung process, what
>>> should I be doing to determine the calling/offending function.
>> 
>> Build a cygwin1.dll with debug symbols and then use addr2line.  Or use
>> strace.  At the very least you should try the latest snapshot to see if
>> it fixes your problem. 
>> 
> 
> 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?

  I may not be Brian, but I like to use

make CPPFLAGS_FOR_TARGET='-g -O0' CFLAGS_FOR_TARGET='-g -O0'
CXXFLAGS_FOR_TARGET='-g -O0' all 2>&1 | tee build.log
 
which gets you an unoptimised debug build.  Killing optimisation makes
stepping through the source much easier as it doesn't jump around all over
the place.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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