This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
RE: Building Insight snapshot on CygWin?
- From: "Kevin Powell" <KPowell at sirf dot com>
- To: <insight at sources dot redhat dot com>
- Date: Mon, 23 Jun 2003 16:15:07 -0700
- Subject: RE: Building Insight snapshot on CygWin?
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 picking up the tcl and tk configurations properly, so I had to manually configure 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/libdejagnu'
c++ -DPACKAGE=\"dejagnu\" -DVERSION=\"1.4.2\" -I. -I../../../../insight+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 =
char, _Traits = std::char_traits<char>]' is protected
../../../../insight+dejagnu-20030621/dejagnu/testsuite/libdejagnu/unit.cc:56: 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 insight 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 failed 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 conditions.
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=00426010
eax=004C5EB2 ebx=50401000 ecx=0022DA00 edx=10147FA0 esi=10141E08 edi=00000002
ebp=0022D738 esp=0022D710 program=C:\cygwin\usr\local\bin\gdb.exe
cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
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 conditions.
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