From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28441 invoked by alias); 4 Dec 2003 15:59:33 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Reply-To: cygwin-xfree@cygwin.com Received: (qmail 28434 invoked from network); 4 Dec 2003 15:59:33 -0000 Received: from unknown (HELO central.ixn.com) (65.19.132.2) by sources.redhat.com with SMTP; 4 Dec 2003 15:59:33 -0000 Received: from msu.edu (office.ixn.com [68.23.74.57]) (authenticated bits=0) by central.ixn.com (8.12.10/8.12.10) with ESMTP id hB4FxRDN008867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Dec 2003 10:59:29 -0500 (EST) Message-ID: <3FCF59DC.30301@msu.edu> Date: Thu, 04 Dec 2003 15:59:00 -0000 From: Harold L Hunt II User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin-xfree@cygwin.com CC: bug-ddd@gnu.org Subject: Re: DDD 3.3.8 (i686-pc-cygwin) gets `Segmentation fault WAS Re: c ompiling DDD References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.5 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) X-SW-Source: 2003-12/txt/msg00047.txt.bz2 List-Id: Richard Campbell wrote: >>The problem is not with Cygwin's LessTif... the problem is in how DDD is >>detecting LessTif on Cygwin. It must be assuming that the file name for >>the import library with be of the format foo.a whereas the name is of >>the format foo.dll.a on Cygwin. > > > This would be detection inside the actual execution, then? The link step > is libtoolized and ends up being: > > g++ -DNDEBUG -O2 -g -W -Wall -trigraphs -o ddd.exe ddd.o basename.o > compare.o cook.o cwd.o glob.o > > UndoBuffer.o UndoBE.o WhatNextCB.o configinfo.o -L/usr/X11R6/lib > .libs/libimp-cygXm-2.a -lXft -lXrender .libs/libimp-cygfontconfig-1.a > .libs/libimp-cygfreetype-6.a -lz .libs/libimp-cygexpat-0.a -lXaw -lXmu -lXt > -lXpm -lXp -lXext -lX11 -lSM -lICE -lncurses -ly ../libiberty/libiberty.a > -Wl,--rpath -Wl,/usr/X11R6/lib -Wl,--rpath -Wl,/usr/X11R6/lib > > Which looks sorta automagic for the dlls, right? I'm not an expert (or even a user of DDD), but it wouldn't be the first time if I saw something detected incorrectly in configure (picking Motif versus LessTif), followed by a clean compile, followed by a crash on execution. Remember, Motif and LessTif are supposed to have the same interface, so code written for either should compile and link against the other, but the code may not work (segfault). So, I would suspect that DDD's configure is detecting Motif (or assuming Motif by default), compiling some conditional segments for Motif instead of for LessTif (introducing buggy code), followed by linking with LessTif (leading to a crash when the code that works with Motif but not LessTif is run). Again, this is speculation, but that is where I would be looking at the moment. Harold