Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Markus Hoenicka" <Markus DOT Hoenicka AT uth DOT tmc DOT edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15445.31689.768000.497720@gargle.gargle.HOWL>
Date: Mon, 28 Jan 2002 16:26:49 +0000
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>, cygwin AT cygwin DOT com
Subject: Re: C++ dll segfault problem
In-Reply-To: <044e01c1a72b$8f8eb050$0200a8c0@lifelesswks>
References: <15437 DOT 57169 DOT 404000 DOT 997498 AT gargle DOT gargle DOT HOWL>
	<044e01c1a72b$8f8eb050$0200a8c0 AT lifelesswks>
X-Mailer: VM 6.94 under Emacs 20.6.1

Hi Robert,

I didn't know this nice trick. However, neither sh nor bash can
reproduce this problem under these conditions. The apps just run
fine. But if I start the apps without strace, they segfault upon exit.

Does this funny behaviour give any clue about the nature of the
underlying problem? Are there any other tricks to debug this?

thanks
Markus

Robert Collins writes:
 > Try this:
 > strace -ofoo.log -f -n <cygwinroot>\bin\sh.exe <command to run>
 > 
 > That should reproduce the fault, if it doesn't, try bash instead sh.

-- 
Markus Hoenicka, PhD
UT Houston Medical School
Dept. of Integrative Biology and Pharmacology
6431 Fannin MSB4.114
Houston, TX 77030
(713) 500-6313, -7477
(713) 500-7444 (fax)
Markus DOT Hoenicka AT uth DOT tmc DOT edu
http://ourworld.compuserve.com/homepages/hoenicka_markus/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/