Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <40107AD3.8070900@acm.org> Date: Thu, 22 Jan 2004 17:37:23 -0800 From: David Rothenberger User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: bash, dircolors, setsid and a stackdump References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Rafael Kitover wrote: > I would dearly love to know how you get those lovely line numbers in the > stackdump :) I used the unstripped DLL from my CVS build and then used addr2line on each function address in the stacktrace, specifying the DLL as the executable. I.e., addr2line -e /bin/cygwin1.dll
I don't know whether it's necessary to be running the unstripped DLL when the stacktrace is generated, but I was. I have since discovered that while dircolors does cause the stackdump, the problem is not dircolors. With that line commented from /etc/profile, I don't get a stackdump but the script does not complete its execution. I determined this by executing the script ---begin script--- #!/bin/sh echo foo > t sleep 10 ---end script--- and noting that t was created but of zero length. Dave -- 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/