From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31308 invoked by alias); 23 Jun 2003 23:18:41 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 26149 invoked from network); 23 Jun 2003 23:15:23 -0000 Received: from unknown (HELO sjexchange.sirf.com) (12.33.2.18) by sources.redhat.com with SMTP; 23 Jun 2003 23:15:23 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Building Insight snapshot on CygWin? Date: Mon, 23 Jun 2003 23:18:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Kevin Powell" To: X-SW-Source: 2003-q2/txt/msg00181.txt.bz2 Hi -- I'm not on this list, but I have recently compiled insight for Cygwin= using the 20030621 snapshot. FWIW, here are my results: First -- I got the same message as Gordon Shumacher when building dejagnu: configure: error: source directory already configured; run make distclean there first configure: error: /usr/src/insight+dejagnu-20030520/dejagnu/example/calc/configure failed for example/calc make: *** [configure-dejagnu] Error 1 re-running make seemed to make this go away. Second, I had problems with expect. the expect configure script was not pi= cking up the tcl and tk configurations properly, so I had to manually confi= gure expect with --with-tk-config and --with-tcl-config, then I was able to= get past building expect. The rest of the main build went pretty smoothly. make check fails thusly: make[6]: Entering directory `/usr/src/insight/insight/dejagnu/testsuite/lib= dejagnu' c++ -DPACKAGE=3D\"dejagnu\" -DVERSION=3D\"1.4.2\" -I. -I../../../../insigh= t+dejagnu-20030621/dejagnu/testsuite/libdejagnu -g -O2 -c ../../../../= insight+dejagnu-20030621/dejagnu/testsuite/libdejagnu/unit.cc /usr/include/c++/3.2/streambuf: In function `int main(int, char**)': /usr/include/c++/3.2/streambuf:416: `std::basic_streambuf<_CharT, _Traits>* std::basic_streambuf<_CharT, _Traits>::setbuf(_CharT*, int) [with _CharT= =3D char, _Traits =3D std::char_traits]' is protected ../../../../insight+dejagnu-20030621/dejagnu/testsuite/libdejagnu/unit.cc:5= 6: within this context make[6]: *** [unit.o] Error 1 Having read that dejagnu was probably broken for cygwin, I didn't bother to= try to fix this. Perhaps that was a bad idea, because my newly built insig= ht cannot debug my program. It crashes as soon as I try to run the target = program. I'll attach the stackdump, though I think it won't be helpful. I= tried to use the cygwin dumper utility to get a core file and use that to = further isolate the problem (can one use gdb to debug gdb?), but that faile= d as well (dumper core dumped before generating the core file). here's what gdb self reports: $ /usr/local/bin/gdb -v GNU gdb 20030621 Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-cygwin". Here's the stackdump: Exception: STATUS_ACCESS_VIOLATION at eip=3D00426010 eax=3D004C5EB2 ebx=3D50401000 ecx=3D0022DA00 edx=3D10147FA0 esi=3D10141E08 = edi=3D00000002 ebp=3D0022D738 esp=3D0022D710 program=3DC:\cygwin\usr\local\bin\gdb.exe cs=3D001B ds=3D0023 es=3D0023 fs=3D0038 gs=3D0000 ss=3D0023 Stack trace: Frame Function Args 0022D738 00426010 (10141E08, 0022D9E8, 00000000, 0042E128) 0022D778 00426222 (10141E08, 0022D9E8, 00000000, 00000000) 0022D7A8 004269CC (102ECD24, 00000000, 0022D9E8, 00000000) 0022D7D8 00426A7D (102ECD24, 00000000, 0022D9E8, 00000000) 0022D808 004B8273 (0022D9A0, 00000000, 0022D948, 00422770) 0022D818 004228B1 (10122F30, 0022D980, 0022D924, 6107CD49) 0022D948 00422770 (004228A0, 10122F30, 0022D980, 0022D97C) 0022D988 0042290A (004B8220, 0022D9A0, 004B8307, 00000002) 0022D9C8 004B83A5 (102ECD24, 00000000, 0022D9E8, 00000000) 0022D9F8 004B8AFF (102ECD24, 50401000, 50401000, 004C5EB2) End of stack trace If there is some obvious bit of information that explains all this (eg, the= snapshot I used is known to be busted), please let me know. Anyway, I've fallen back on using the distributed binary version of insight= for cygwin. I have noted that the binary package gives this self-report $ /usr/bin/gdb -v GNU gdb 2003-03-03-cvs (cygwin-special) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-cygwin". I guess that to build my own, I need whatever makes the standard GDB into a= cygwin-special gdb. Kevin Powell