RE: Building Insight snapshot on CygWin?

RE: Building Insight snapshot on CygWin?

[Kevin Powell]

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

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

On Mon, 2003-06-23 at 16:15, Kevin Powell wrote:
> 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.

Sigh. I was under the impression that someone had fixed this.

> 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

Of course, this has nothing to do with insight. I would harrass the
dejagnu maintainer about the problems. :-)

> Here's the stackdump:

[snip]

Make sure that you don't build Insight with optimization and run it
under gdb. When the error occurs, gdb will stop the process immediately.
You should have a valid, readable stack backtrace (unless it was
corrupted, of course). Use the distributed gdb to run the "bad" one.

BTW, can you describe what you're doing to crash it? (aka: test case).
Although I have not extensively tested on cygwin in a while, I do some
basic sanity checking, debugging insight with insight.

> I guess that to build my own, I need whatever makes the standard GDB into a cygwin-special gdb.

There is no difference of which I am aware. I think it's just
nomenclature.

I guess I'm just lucky? I still cannot reproduce any of these cygwin
errors (the Win98 and dejagnu problems excepted). Argh. I think this is
at least as frustrating for me as it is for everyone else. :v(

Keith

PS. If you're using CVS snapshots/CVS HEAD: make sure you get my patch
to src/Makefile.in. There was a small configury error which I never saw
because I had installed versions of insight (and tcl, tk, itcl, etc)
available. When configuring the gdb directory, make sure that "looking
for private itcl headers"-like stuff comes from the src directory and
not some random package on the system.

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

On Mon, 2003-07-07 at 12:44, John Lowen wrote:

> The build hangs indefinitely at this point. Keith Seitz reported on Jun 11 that he tried it and that Windows98 was really messed up with regards to this problem. Has there been any further investigation?

I've have not investigated this any further yet. I'm in the middle of a
really hectic month, and the best I could do is offer condolences right
now. If someone can find out exactly what causes the problems (a small
testcase would absolutely perfect), we can at least get the bug to the
right people.

> I may try to build under XP and see if I'm successful there. I am open to any suggestions.
> 

It build fine for me under Win2k. I've heard reports that XP should
work, too. (I think the main cygwin distro is built on XP.)

Keith

RE: Building Insight snapshot on CygWin?

[John Lowen]

I experienced a problem that was reported earlier on the mail-list regarding a build of Insight under Win98/Cygwin. The build stopped at the following point:

checking whether to build shared libraries... no
checking whether to build static libraries... yes


The build hangs indefinitely at this point. Keith Seitz reported on Jun 11 that he tried it and that Windows98 was really messed up with regards to this problem. Has there been any further investigation?

I may try to build under XP and see if I'm successful there. I am open to any suggestions.

John


John Lowen
AMT-Datasouth
jlowen@amtdatasouth.com
http://www.amtdatasouth.com
(704)523-8500 ext. 132

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

On Mon, 2003-06-23 at 18:45, Kevin Powell wrote:
> As promised, here is the result of using an unoptimized insight/gdb.  BTW, thanks for the tip on turning off the optimizations.  At least now I can get a usable (not to me, but maybe to others) backtrace.
>
> The executive summary is that the unoptimized gdb behaves a bit better than my first attempt.  At least now I can set a breakpoint and run to it. However, the first time I try to step, gdb crashes with the same segfault as before.  And, to answer your question from the last email, it really is gdb that is crashing -- the target program runs fine both under the distributed gdb and outside of the debugger.  And, now I know the reason why it crashes:  
> 

This is perfect! Insight isn't even in the backtrace! :-)

Please send/forward your excellent message to the gdb list. They've been
churning the dwarf2 readers for a little while now, and it looks like
you've either uncovered a bug or are missing a recent patch.

In either case, the whizzes on the gdb list (gdb at sources dot redhat
dot com) will be able to guide you better.

Keith

PS. Your message is perfect! An example session and a backtrace! How
refreshing!

RE: Building Insight snapshot on CygWin?

[Kevin Powell]

Keith,

As promised, here is the result of using an unoptimized insight/gdb.  BTW, thanks for the tip on turning off the optimizations.  At least now I can get a usable (not to me, but maybe to others) backtrace.

The executive summary is that the unoptimized gdb behaves a bit better than my first attempt.  At least now I can set a breakpoint and run to it. However, the first time I try to step, gdb crashes with the same segfault as before.  And, to answer your question from the last email, it really is gdb that is crashing -- the target program runs fine both under the distributed gdb and outside of the debugger.  And, now I know the reason why it crashes:  

gdb/dwarf2-frame.c:508 fs->data_align = fde->cie->data_alignment_factor;

it turns out that fde->cie is NULL.  Why this might happen requires, I think, some knowledge of how gdb internals work, and I have no such knowledge.
 
The following text captures my attempt to run my broken gdb inside of the working distributed gdb.

$ /usr/bin/gdb /usr/local/bin/gdb
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"...
(gdb) run
Starting program: /usr/local/bin/gdb.exe
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".
(gdb) file HelloWorld.exe
Reading symbols from HelloWorld.exe...done.
(gdb) break main
Breakpoint 1 at 0x4010bc: file HelloWorld.c, line 5.
(gdb) run
Starting program: /home/Administrator/testing/HelloWorld.exe

Breakpoint 1, main (argc=1, argv=0xa042a68) at HelloWorld.c:5
5               printf ("Hello World!\n");
(gdb) n

Program received signal SIGSEGV, Segmentation fault.
0x0057f581 in dwarf2_frame_cache (next_frame=0x101231b8, this_cache=0x10123224)
at ../../insight+dejagnu-20030621/gdb/dwarf2-frame.c:508
508       fs->data_align = fde->cie->data_alignment_factor;
(gdb) bt
#0  0x0057f581 in dwarf2_frame_cache (next_frame=0x101231b8, this_cache=0x10123224) at ../../insight+dejagnu-20030621/gdb/dwarf2-frame.c:508
#1  0x0057f980 in dwarf2_frame_this_id (next_frame=0x101231b8, this_cache=0x10123224, this_id=0x10123240) at ../../insight+dejagnu-20030621/gdb/dwarf2-frame.c:599
#2  0x00464398 in get_frame_id (fi=0x10123210) at ../../insight+dejagnu-20030621/gdb/frame.c:243
#3  0x0043a1d6 in step_1 (skip_subroutines=1, single_inst=0, count_string=0x0) at ../../insight+dejagnu-20030621/gdb/infcmd.c:631
#4  0x00439f7b in next_command (count_string=0x0, from_tty=1) at ../../insight+dejagnu-20030621/gdb/infcmd.c:559
#5  0x00405a9b in do_cfunc (c=0x1010e130, args=0x0, from_tty=1) at ../../insight+dejagnu-20030621/gdb/cli/cli-decode.c:53
#6  0x00408157 in cmd_func (cmd=0x1010e130, args=0x0, from_tty=1) at ../../insight+dejagnu-20030621/gdb/cli/cli-decode.c:1517
#7  0x00424d8a in execute_command (p=0x10102ce9 "", from_tty=1) at ../../insight+dejagnu-20030621/gdb/top.c:716
#8  0x0048bd6a in command_handler (command=0x10102ce8 "n") at ../../insight+dejagnu-20030621/gdb/event-top.c:500
#9  0x0048c58b in command_line_handler (rl=0x1011c8e8 "D{\023\020") at ../../insight+dejagnu-20030621/gdb/event-top.c:793
#10 0x00601680 in rl_callback_read_char () at ../../insight+dejagnu-20030621/readline/callback.c:123
#11 0x0048b3ab in rl_callback_read_char_wrapper (client_data=0x0) at ../../insight+dejagnu-20030621/gdb/event-top.c:166
#12 0x0048bb97 in stdin_event_handler (error=0, client_data=0x0) at ../../insight+dejagnu-20030621/gdb/event-top.c:416
#13 0x004a75ab in handle_file_event (event_file_desc=0) at ../../insight+dejagnu-20030621/gdb/event-loop.c:721
#14 0x004a6d95 in process_event () at ../../insight+dejagnu-20030621/gdb/event-loop.c:334
#15 0x004a6dde in gdb_do_one_event (data=0x0) at ../../insight+dejagnu-20030621/gdb/event-loop.c:371
#16 0x004248be in do_catch_errors (uiout=0x10125708, data=0x22f868) at ../../insight+dejagnu-20030621/gdb/top.c:497
#17 0x004246be in catcher (func=0x4248a2 <do_catch_errors>, func_uiout=0x10125708, func_args=0x22f868, func_val=0x22f874, func_caught=0x22f870, errstring=0x4a6df7 "", mask=6) at ../../insight+dejagnu-20030621/gdb/top.c:429
#18 0x0042490a in catch_errors (func=0x4a6daa <gdb_do_one_event>, func_args=0x0, errstring=0x4a6df7 "", mask=6) at ../../insight+dejagnu-20030621/gdb/top.c:509
#19 0x004a6e23 in start_event_loop () at ../../insight+dejagnu-20030621/gdb/event-loop.c:397
#20 0x0048b4b9 in cli_command_loop () at ../../insight+dejagnu-20030621/gdb/event-top.c:198
#21 0x004428cd in current_interp_command_loop () at ../../insight+dejagnu-20030621/gdb/interps.c:279
#22 0x0040110b in captured_command_loop (data=0x0) at ../../insight+dejagnu-20030621/gdb/main.c:97
#23 0x004248be in do_catch_errors (uiout=0x10125708, data=0x22fa58) at ../../insight+dejagnu-20030621/gdb/top.c:497
#24 0x004246be in catcher (func=0x4248a2 <do_catch_errors>, func_uiout=0x10125708, func_args=0x22fa58, func_val=0x22fa64, func_caught=0x22fa60, errstring=0x401260 "", mask=6) at ../../insight+dejagnu-20030621/gdb/top.c:429
#25 0x0042490a in catch_errors (func=0x401100 <captured_command_loop>, func_args=0x0, errstring=0x401260 "", mask=6) at ../../insight+dejagnu-20030621/gdb/top.c:509
#26 0x0040263d in captured_main (data=0x22fd98) at ../../insight+dejagnu-20030621/gdb/main.c:811
#27 0x004248be in do_catch_errors (uiout=0x677420, data=0x22fd38) at ../../insight+dejagnu-20030621/gdb/top.c:497
#28 0x004246be in catcher (func=0x4248a2 <do_catch_errors>, func_uiout=0x677420, func_args=0x22fd38, func_val=0x22fd44, func_caught=0x22fd40, errstring=0x401260 "", mask=6) at ../../insight+dejagnu-20030621/gdb/top.c:429
#29 0x0042490a in catch_errors (func=0x4014be <captured_main>, func_args=0x22fd98, errstring=0x401260 "", mask=6) at ../../insight+dejagnu-20030621/gdb/top.c:509
#30 0x00402674 in gdb_main (args=0x22fd98) at ../../insight+dejagnu-20030621/gdb/main.c:820
#31 0x004010f6 in main (argc=1, argv=0x10102a68) at ../../insight+dejagnu-20030621/gdb/gdb.c:35
(gdb)

And in the next gdb session (since I forgot to do this on the first run:)

(gdb) info args
next_frame = (struct frame_info *) 0x101231b8
this_cache = (void **) 0x10123224
(gdb) info locals
old_chain = (struct cleanup *) 0x1011c778
num_regs = 40
cache = (struct dwarf2_frame_cache *) 0x101232b8
fs = (struct dwarf2_frame_state *) 0x102056e0
fde = (struct dwarf2_fde *) 0x10151db8
reg = 6
(gdb) p fde->cie
$1 = (struct dwarf2_cie *) 0x0
(gdb)

Kevin Powell

-----Original Message-----
From: Keith Seitz
Sent: Monday, June 23, 2003 6:18 PM
To: Kevin Powell
Cc: insight@sources.redhat.com
Subject: RE: Building Insight snapshot on CygWin?


On Mon, 2003-06-23 at 17:14, Kevin Powell wrote:
> Starting program: /home/Administrator/testing/HelloWorld.exe
>      58 [main] gdb 2348 handle_exceptions: Error while dumping state (probably corrupted stack)
> Segmentation fault (core dumped)

Yeah, that doesn't look promising, eh? ;-)

One quick question: did you really do this with "gdb HelloWorld.exe"? In
other words, gdb itself crashes trying to debug this?

> Note that it is gdb segfaulting there, not HelloWorld.  So, any clues there? Am I totally braindead?  

I don't think your out of your mind. Well, at least you're not alone!

> Does insight get compiled with optimization on by default? In any case, I'm reconfiguring with CFLAGS=-g -O0 right now.  I'll post results in a bit.

Yes, that's right: the toolchain, by default, uses -O2. You can
configure with CFLAGS="-g" or something to supress it (this is how I do
it):

$ CFLAGS="-g" /path/to/src/configure --prefix=...

Keith

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

On Mon, 2003-06-23 at 17:14, Kevin Powell wrote:
> Starting program: /home/Administrator/testing/HelloWorld.exe
>      58 [main] gdb 2348 handle_exceptions: Error while dumping state (probably corrupted stack)
> Segmentation fault (core dumped)

Yeah, that doesn't look promising, eh? ;-)

One quick question: did you really do this with "gdb HelloWorld.exe"? In
other words, gdb itself crashes trying to debug this?

> Note that it is gdb segfaulting there, not HelloWorld.  So, any clues there? Am I totally braindead?  

I don't think your out of your mind. Well, at least you're not alone!

> Does insight get compiled with optimization on by default? In any case, I'm reconfiguring with CFLAGS=-g -O0 right now.  I'll post results in a bit.

Yes, that's right: the toolchain, by default, uses -O2. You can
configure with CFLAGS="-g" or something to supress it (this is how I do
it):

$ CFLAGS="-g" /path/to/src/configure --prefix=...

Keith

RE: Building Insight snapshot on CygWin?

[Kevin Powell]

Keith, 

Here is the result of running my "home-baked" gdb/insight on the standard hello world program:

$ cat HelloWorld.c && gcc -g -o HelloWorld.exe HelloWorld.c && ./HelloWorld.exe
#include <stdio.h>

int main(int argc, char **argv) {

        printf ("Hello World!\n");
}

Hello World!

$ /usr/local/bin/gdb HelloWorld.exe
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"...
(gdb) break main
Breakpoint 1 at 0x4010bc: file HelloWorld.c, line 5.
(gdb) run
Starting program: /home/Administrator/testing/HelloWorld.exe
     58 [main] gdb 2348 handle_exceptions: Error while dumping state (probably corrupted stack)
Segmentation fault (core dumped)


Note that it is gdb segfaulting there, not HelloWorld.  So, any clues there? Am I totally braindead?  

Does insight get compiled with optimization on by default? In any case, I'm reconfiguring with CFLAGS=-g -O0 right now.  I'll post results in a bit.

Kevin Powell

On Mon, 2003-06-23 at 16:15, Kevin Powell wrote:
> 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.

Sigh. I was under the impression that someone had fixed this.

> 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

Of course, this has nothing to do with insight. I would harrass the
dejagnu maintainer about the problems. :-)

> Here's the stackdump:

[snip]

Make sure that you don't build Insight with optimization and run it
under gdb. When the error occurs, gdb will stop the process immediately.
You should have a valid, readable stack backtrace (unless it was
corrupted, of course). Use the distributed gdb to run the "bad" one.

BTW, can you describe what you're doing to crash it? (aka: test case).
Although I have not extensively tested on cygwin in a while, I do some
basic sanity checking, debugging insight with insight.

> I guess that to build my own, I need whatever makes the standard GDB into a cygwin-special gdb.

There is no difference of which I am aware. I think it's just
nomenclature.

I guess I'm just lucky? I still cannot reproduce any of these cygwin
errors (the Win98 and dejagnu problems excepted). Argh. I think this is
at least as frustrating for me as it is for everyone else. :v(

Keith

PS. If you're using CVS snapshots/CVS HEAD: make sure you get my patch
to src/Makefile.in. There was a small configury error which I never saw
because I had installed versions of insight (and tcl, tk, itcl, etc)
available. When configuring the gdb directory, make sure that "looking
for private itcl headers"-like stuff comes from the src directory and
not some random package on the system.

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

Ok, I've checked this on cygwin on Windows 98.

Short story: Win98 is really messed up.

Whatever opcodes/ does with perl, it causes perl to crash on Windows 98
systems.

Ignoring that, configure does just "stop" when it gets to the part about
checking whether to build shared libraries.

I have not had time to investigate yet, but it is definitely a Windows
98 issue with cygwin.

Keith

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

On Mon, 2003-06-09 at 08:53, Schumacher, Gordon wrote:
> I'm afraid that I'm running on Windows 2000, so thus am also running a
> NT-kernel-based version.  Perhaps this is an NT versus 9x issue?

That is also what I use, but my box does have a copy of Win98 on it,
too. Maybe I'll try to boot it up today and install a fresh copy of
cygwin onto it and try the build...

Keith

RE: Building Insight snapshot on CygWin?

[Schumacher, Gordon]

I'm afraid that I'm running on Windows 2000, so thus am also running a
NT-kernel-based version.  Perhaps this is an NT versus 9x issue?

# -----Original Message-----
# From: vadraj kulkarni [mailto:vadiraj_kulkarni@lycos.com]
# Sent: Monday, June 09, 2003 3:28 AM
# To: Schumacher, Gordon
# Cc: insight@sources.redhat.com
# Subject: RE: Building Insight snapshot on CygWin?
# 
# 
# Hello Sir,
# May i know the OS (windows  version) you have used to bring 
# insight on cygwin?.
# I am able to successfully bring insight up on windows-XP. I 
# am not able to bring on windows-98.
# I am facing the below problems.
# 
# 1). Wheni do ../configure --target......
# I will get windows error message saying "This program has 
# perfomed illega...."
# after displaying below message.
# ...
# Checking for working autoheader...
# 
# 
# 2). If i discard the above error message, then configure will 
# stop after displaying below message.
# 
# .....
# Finding the maximum length of command line arguments.....
# 
# 
# 3). Sometimes, i don't get error nuber-2. At that time, 
# application will hang after displaying below message.
# 
# .....
# Checking whether to build static library.... yes
# 
# 
# 
# If you know why this problem comes, please tell me.
# I will be eagerly waiting for your reply.
# 
# thanks & regards
# vadiraj
# 
# 
# 
# 
# 
# --
# 
# --------- Original Message ---------
# 
# DATE: Thu, 5 Jun 2003 10:42:41 
# From: "Schumacher, Gordon" <gordon_schumacher@maxtor.com>
# To: "'vadiraj_kulkarni@lycos.com'" <vadiraj_kulkarni@lycos.com>
# Cc: 
# 
# >Well...
# >
# >I've not had great luck building the 5.3 version; I've 
# successfully built
# >the 20030602 snapshot, though, both as a native and as a DOS32
# >cross-debugger.
# >
# >I've attached the process I use.  To build natively, you 
# don't need to build
# >binutils, and for the cross-debugger, you should change 
# "target", of course.
# >Hope this helps!
# >
# ># -----Original Message-----
# ># From: vadraj kulkarni [mailto:vadiraj_kulkarni@lycos.com]
# ># Sent: Wednesday, June 04, 2003 11:50 PM
# ># To: Schumacher, Gordon
# ># Subject: RE: Building Insight snapshot on CygWin?
# ># 
# ># 
# ># 
# ># Hi,
# ># Yes. I want to have cross-debugger on cygwin?. Before 
# ># building cross-debugger, first i want to compile for i686 
# ># itself. Can you please answer my doubts?.
# ># 
# ># 
# ># Thanks
# ># vadiraj
# ># 
# ># --
# ># 
# ># --------- Original Message ---------
# ># 
# ># DATE: Wed, 4 Jun 2003 08:51:52 
# ># From: "Schumacher, Gordon" <gordon_schumacher@maxtor.com>
# ># To: "'vadiraj_kulkarni@lycos.com'" <vadiraj_kulkarni@lycos.com>
# ># Cc: 
# ># 
# ># >Ah - are you trying to build a cross-debugger?  What is your 
# ># goal for this?
# ># >
# ># ># -----Original Message-----
# ># ># From: vadraj kulkarni [mailto:vadiraj_kulkarni@lycos.com]
# ># ># Sent: Wednesday, June 04, 2003 5:03 AM
# ># ># To: Schumacher, Gordon
# ># ># Subject: RE: Building Insight snapshot on CygWin?
# ># ># 
# ># ># 
# ># ># Hello,
# ># ># This is not the reply to your query. Rather i need some help 
# ># ># on building insight on windows.
# ># ># I learnt from your previous mail that you are able to 
# ># ># configure and install insight successfully on windwos system.
# ># ># 
# ># ># I have also installed cygwin  on windows-98 system. 
# ># ># Unfortunately i am not able to run configure on 
# ># ># insight-5.1,5.2 ,5.3. Infact i tried getting 5.3 snapshots 
# ># ># from CVS server of sources.redhat.com
# ># ># 
# ># ># Configuration will stop in between after saying "checking for 
# ># ># support of static lib... yes"
# ># ># 
# ># ># So i want a favour from you regarding how to build insight on 
# ># ># cygwin. Which OS you have used, insight version,etc. Please 
# ># ># try to give info on this as soon as possible.
# ># ># 
# ># ># thanks & regards
# ># ># vadiraj
# ># ># 
# ># ># 
# ># ># 
# ># ># 
# ># ># 
# ># ># 
# ># ># ____________________________________________________________
# ># ># Get advanced SPAM filtering on Webmail or POP Mail ... Get 
# ># Lycos Mail!
# ># ># http://login.mail.lycos.com/r/referral?aid=27005
# ># ># 
# ># >
# ># 
# ># 
# ># 
# ># ____________________________________________________________
# ># Get advanced SPAM filtering on Webmail or POP Mail ... Get 
# Lycos Mail!
# ># http://login.mail.lycos.com/r/referral?aid=27005
# ># 
# >
# >
# 
# 
# 
# ____________________________________________________________
# Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
# http://login.mail.lycos.com/r/referral?aid=27005
# 

RE: Building Insight snapshot on CygWin?

[vadraj kulkarni]

Hello Sir,
May i know the OS (windows  version) you have used to bring insight on cygwin?.
I am able to successfully bring insight up on windows-XP. I am not able to bring on windows-98.
I am facing the below problems.

1). Wheni do ../configure --target......
I will get windows error message saying "This program has perfomed illega...."
after displaying below message.
...
Checking for working autoheader...


2). If i discard the above error message, then configure will stop after displaying below message.

.....
Finding the maximum length of command line arguments.....


3). Sometimes, i don't get error nuber-2. At that time, application will hang after displaying below message.

.....
Checking whether to build static library.... yes



If you know why this problem comes, please tell me.
I will be eagerly waiting for your reply.

thanks & regards
vadiraj





--

--------- Original Message ---------

DATE: Thu, 5 Jun 2003 10:42:41 
From: "Schumacher, Gordon" <gordon_schumacher@maxtor.com>
To: "'vadiraj_kulkarni@lycos.com'" <vadiraj_kulkarni@lycos.com>
Cc: 

>Well...
>
>I've not had great luck building the 5.3 version; I've successfully built
>the 20030602 snapshot, though, both as a native and as a DOS32
>cross-debugger.
>
>I've attached the process I use.  To build natively, you don't need to build
>binutils, and for the cross-debugger, you should change "target", of course.
>Hope this helps!
>
># -----Original Message-----
># From: vadraj kulkarni [mailto:vadiraj_kulkarni@lycos.com]
># Sent: Wednesday, June 04, 2003 11:50 PM
># To: Schumacher, Gordon
># Subject: RE: Building Insight snapshot on CygWin?
># 
># 
># 
># Hi,
># Yes. I want to have cross-debugger on cygwin?. Before 
># building cross-debugger, first i want to compile for i686 
># itself. Can you please answer my doubts?.
># 
># 
># Thanks
># vadiraj
># 
># --
># 
># --------- Original Message ---------
># 
># DATE: Wed, 4 Jun 2003 08:51:52 
># From: "Schumacher, Gordon" <gordon_schumacher@maxtor.com>
># To: "'vadiraj_kulkarni@lycos.com'" <vadiraj_kulkarni@lycos.com>
># Cc: 
># 
># >Ah - are you trying to build a cross-debugger?  What is your 
># goal for this?
># >
># ># -----Original Message-----
># ># From: vadraj kulkarni [mailto:vadiraj_kulkarni@lycos.com]
># ># Sent: Wednesday, June 04, 2003 5:03 AM
># ># To: Schumacher, Gordon
># ># Subject: RE: Building Insight snapshot on CygWin?
># ># 
># ># 
># ># Hello,
># ># This is not the reply to your query. Rather i need some help 
># ># on building insight on windows.
># ># I learnt from your previous mail that you are able to 
># ># configure and install insight successfully on windwos system.
># ># 
># ># I have also installed cygwin  on windows-98 system. 
># ># Unfortunately i am not able to run configure on 
># ># insight-5.1,5.2 ,5.3. Infact i tried getting 5.3 snapshots 
># ># from CVS server of sources.redhat.com
># ># 
># ># Configuration will stop in between after saying "checking for 
># ># support of static lib... yes"
># ># 
># ># So i want a favour from you regarding how to build insight on 
># ># cygwin. Which OS you have used, insight version,etc. Please 
># ># try to give info on this as soon as possible.
># ># 
># ># thanks & regards
># ># vadiraj
># ># 
># ># 
># ># 
># ># 
># ># 
># ># 
># ># ____________________________________________________________
># ># Get advanced SPAM filtering on Webmail or POP Mail ... Get 
># Lycos Mail!
># ># http://login.mail.lycos.com/r/referral?aid=27005
># ># 
># >
># 
># 
># 
># ____________________________________________________________
># Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
># http://login.mail.lycos.com/r/referral?aid=27005
># 
>
>



____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

On Tue, 2003-06-03 at 13:02, Schumacher, Gordon wrote:

> About 90% of the time, option buttons and checkboxes don't change state upon
> being clicked.  They highlight - but the check doesn't change.  Option
> buttons usually contain *neither* setting.

> I can connect to an application via Remote/Serial, but when it hits a
> breakpoint, the main window says only "Select a function to disassemble".  I
> can pick a source file, but I can't seem to get it to indicate where it is
> stopped at (i.e., no "you are here" highlight.)  Single-stepping does
> nothing; continue and "step asm" commands seem to do *something* but without
> knowing where the PC is there's not much use to that.

Make sure:
1) Your executable was built with debug info
2) Command-line gdb works

> Would it be helpful to try a Linux to DJGPP cross-debugger and see if that
> works?  I'm not quite sure where to even start looking on this one...!

Couldn't hurt, I suppose. I'd still be curious, though, if command line
gdb works.

Keith

RE: Building Insight snapshot on CygWin?

[Schumacher, Gordon]

# From: Keith Seitz [mailto:keiths@redhat.com]
# Sent: Tuesday, May 27, 2003 12:36 PM
# To: Schumacher, Gordon
# Cc: Insight list (E-mail)
# Subject: RE: Building Insight snapshot on CygWin?
# 
# I don't see any of this. Does libtcl84.a not contain this symbol? What
# does "head config.status" say? Can you do a "make clean; make 
# > make.out
# 2>&1" and send make.out?

Sorry about the delay in replying; I was out for all of last week.

So, I tried snapshot 20030602, and that one builds fine (with dejagnu nuked)
even as a CygWin to i686-pc-msdosdjgpp cross-debugger.  But, now I've got
problems getting it to run properly...

About 90% of the time, option buttons and checkboxes don't change state upon
being clicked.  They highlight - but the check doesn't change.  Option
buttons usually contain *neither* setting.
I can connect to an application via Remote/Serial, but when it hits a
breakpoint, the main window says only "Select a function to disassemble".  I
can pick a source file, but I can't seem to get it to indicate where it is
stopped at (i.e., no "you are here" highlight.)  Single-stepping does
nothing; continue and "step asm" commands seem to do *something* but without
knowing where the PC is there's not much use to that.

Would it be helpful to try a Linux to DJGPP cross-debugger and see if that
works?  I'm not quite sure where to even start looking on this one...!

My cross-binutils package is version 2.13.2, FWIW.

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

On Wed, 2003-05-21 at 13:47, Schumacher, Gordon wrote:
> Creating library file: libtcldde12.a
> tclAppInit.o(.text+0xb0): In function `main':
> /usr/src/insight-20030520/tcl/win/tclAppInit.c:110: undefined reference to
> `__imp__Tcl_Main'

I don't see any of this. Does libtcl84.a not contain this symbol? What
does "head config.status" say? Can you do a "make clean; make > make.out
2>&1" and send make.out?

Keith

Re: Building Insight snapshot on CygWin?

[Andrew Cagney]

> On Wed, 2003-05-21 at 14:42, Keith Seitz wrote:
> 
>> On Wed, 2003-05-21 at 12:02, Martin M. Hunt wrote:
> 
>> > I tried to build the snapshot (on RedHat 9) and it failed on dejagnu. 
>> > So did the May21 snap.
> 
> 
> Yup. Here, too, on linux. (I missed that you said that last time.)
> 
> Ditto for gdb+dejagnu-20030521.tar.bz2. Gordon, please email the gdb
> list (gdb at sources dot redhat dot com). Someone there must know who to
> ping on this.
> 
> I'll see about your insight build troubles on cygwin tomorrow-ish.
> [FWIW, CVS head works just fine...]

dejagnu not building is really a dejagnu problem, from src/MAINTAINERS:

dejagnu/
         Send all patches to:
         http://www.gnu.org/software/dejagnu/
         mail:bug-dejagnu@gnu.org
         For changes to the local repostory, send them to
         gdb-patches@sources.redhat.com when generic; and sid@,
         binutils@, gcc@, etc. for sub-components.

first thing to to is see if the upstream sources already have a fix.

Andrew

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

On Wed, 2003-05-21 at 14:42, Keith Seitz wrote:
> On Wed, 2003-05-21 at 12:02, Martin M. Hunt wrote:
> > I tried to build the snapshot (on RedHat 9) and it failed on dejagnu. 
> > So did the May21 snap.

Yup. Here, too, on linux. (I missed that you said that last time.)

Ditto for gdb+dejagnu-20030521.tar.bz2. Gordon, please email the gdb
list (gdb at sources dot redhat dot com). Someone there must know who to
ping on this.

I'll see about your insight build troubles on cygwin tomorrow-ish.
[FWIW, CVS head works just fine...]

Keith

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

On Wed, 2003-05-21 at 12:02, Martin M. Hunt wrote:
> I tried to build the snapshot (on RedHat 9) and it failed on dejagnu. 
> So did the May21 snap.

Ugh. Something wrong with the snapshot, then, eh? I don't suppose you
tried a GDB snapshot of the same vintage? [Hey, don't I just get to pass
the buck on this to the myriad of people over on the gdb list anyway?
:-)]

Keith

RE: Building Insight snapshot on CygWin?

[Schumacher, Gordon]

# From: Keith Seitz [mailto:keiths@redhat.com]
# Sent: Wednesday, May 21, 2003 11:24 AM
# To: Schumacher, Gordon
# Cc: Insight list (E-mail)
# Subject: RE: Building Insight snapshot on CygWin?
# 
# Ok, I'm kicking off a clean build now of CVS HEAD. Shouldn't be too
# different from the snapshot. I'll report my findings to the list.

I get this:

Creating library file: libtcldde12.a
tclAppInit.o(.text+0xb0): In function `main':
/usr/src/insight-20030520/tcl/win/tclAppInit.c:110: undefined reference to
`__imp__Tcl_Main'
tclAppInit.o(.text+0x101): In function `Tcl_AppInit':
/usr/src/insight-20030520/tcl/win/tclAppInit.c:139: undefined reference to
`__imp__Tcl_Init'
tclAppInit.o(.text+0x135):/usr/src/insight-20030520/tcl/win/tclAppInit.c:147
: undefined reference to `__imp__Tcl_AsyncCreate'
tclAppInit.o(.text+0x15b):/usr/src/insight-20030520/tcl/win/tclAppInit.c:193
: undefined reference to `__imp__Tcl_SetVar'
tclAppInit.o(.text+0x1c1): In function `setargv':
/usr/src/insight-20030520/tcl/win/tclAppInit.c:252: undefined reference to
`__imp__Tcl_Alloc'
tclAppInit.o(.text+0x310): In function `asyncExit':
/usr/src/insight-20030520/tcl/win/tclAppInit.c:333: undefined reference to
`__imp__Tcl_Exit'
tclAppInit.o(.text+0x338): In function `sigHandler':
/usr/src/insight-20030520/tcl/win/tclAppInit.c:368: undefined reference to
`__imp__Tcl_AsyncMark'
collect2: ld returned 1 exit status

Re: Building Insight snapshot on CygWin?

[Martin M. Hunt]

On Wed, 2003-05-21 at 09:54, Schumacher, Gordon wrote:

> When I run that, I get the following:
> 
> configuring in example/calc
> running /bin/sh
> /usr/src/insight+dejagnu-20030520/dejagnu/example/calc/configure
> --build=i686-pc-cygwin --host=i686-pc-cygwin --target=i686-pc-cygwin
> --cache-f
> ile=../../.././config.cache
> --srcdir=/usr/src/insight+dejagnu-20030520/dejagnu/example/calc
> loading cache ../../.././config.cache
> checking for a BSD compatible install... (cached) /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... (cached) yes
> 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

Simplest solution is to rm -rf dejagnu/example/calc and try again. 
Worked for me.

-- 
Martin M. Hunt <hunt@redhat.com>
Red Hat Inc.

RE: Building Insight snapshot on CygWin?

[Martin M. Hunt]

On Wed, 2003-05-21 at 12:00, Keith Seitz wrote:
> On Wed, 2003-05-21 at 10:24, Keith Seitz wrote:
> > Ok, I'm kicking off a clean build now of CVS HEAD. Shouldn't be too
> > different from the snapshot. I'll report my findings to the list.
> 
> Didn't have any problems. Built dejagnu, too. I cannot imagine that
> something has changed in one day...
> 
> Ugh, here we go again: "It works for me." (TM) :-(
> Keith

I tried to build the snapshot (on RedHat 9) and it failed on dejagnu. 
So did the May21 snap.

-- 
Martin M. Hunt <hunt@redhat.com>
Red Hat Inc.

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

On Wed, 2003-05-21 at 10:24, Keith Seitz wrote:
> Ok, I'm kicking off a clean build now of CVS HEAD. Shouldn't be too
> different from the snapshot. I'll report my findings to the list.

Didn't have any problems. Built dejagnu, too. I cannot imagine that
something has changed in one day...

Ugh, here we go again: "It works for me." (TM) :-(
Keith

RE: Building Insight snapshot on CygWin?

[Keith Seitz]

On Wed, 2003-05-21 at 10:18, Schumacher, Gordon wrote:
> # FWIW, dejagnu is NOT required to build insight -- only to run 
> # tests. You could always just whack the dejagnu source directory
> # and run the build as normal. Maybe I'll fire up my cygwin box
> # and give this a try -- it's been a few weeks since I tried
> # building there.
> 
> Seems to me that I tried that and got a different set of errors... I'll do
> it again, and come back with that set :)

Ok, I'm kicking off a clean build now of CVS HEAD. Shouldn't be too
different from the snapshot. I'll report my findings to the list.

Keith

RE: Building Insight snapshot on CygWin?

[Schumacher, Gordon]

# From: Keith Seitz [mailto:keiths@redhat.com]
# Sent: Wednesday, May 21, 2003 11:08 AM
# To: Schumacher, Gordon
# Cc: Insight list (E-mail)
# Subject: Re: Building Insight snapshot on CygWin?
# 
# I presume this happens with non-insight on cygwin, too, right?

Hmm, didn't think to try that build.

# FWIW, dejagnu is NOT required to build insight -- only to run 
# tests. You could always just whack the dejagnu source directory
# and run the build as normal. Maybe I'll fire up my cygwin box
# and give this a try -- it's been a few weeks since I tried
# building there.

Seems to me that I tried that and got a different set of errors... I'll do
it again, and come back with that set :)

Re: Building Insight snapshot on CygWin?

[Keith Seitz]

On Wed, 2003-05-21 at 09:54, Schumacher, Gordon wrote:
> Per the procedure above, I'm clearly not building within my source tree, as
> someone else on the list pointed out at one point.  Any idea what in the
> world is going on here?  I'm ultimately trying to build a cross-debugger,
> but the above happens even in native mode!  I've successfully built the
> 5.3.0 tree, but I can't use that because of the Tcl/Tk instabilities.

I presume this happens with non-insight on cygwin, too, right?

From src/MAINTAINERS:

dejagnu/
        Send all patches to:
        http://www.gnu.org/software/dejagnu/
        mail:bug-dejagnu@gnu.org
        For changes to the local repostory, send them to
        gdb-patches@sources.redhat.com when generic; and sid@,
        binutils@, gcc@, etc. for sub-components.

FWIW, dejagnu is NOT required to build insight -- only to run tests. You
could always just whack the dejagnu source directory and run the build
as normal. Maybe I'll fire up my cygwin box and give this a try -- it's
been a few weeks since I tried building there.

Keith

Building Insight snapshot on CygWin?

[Schumacher, Gordon]

I'm trying to build snapshot 20030520 of insight+dejagnu on an up-to-date
CygWin system.  It's aborting with an error in DejaGNU, though... here's my
exact procedure.

cd /usr/src
tar xvfp /d/Storage/GNU/insight+dejagnu-20030520.tar.bz2 --use=bzip2
cd build/gdb
/usr/src/insight+dejagnu-20030520/configure
make -j4 all

When I run that, I get the following:

configuring in example/calc
running /bin/sh
/usr/src/insight+dejagnu-20030520/dejagnu/example/calc/configure
--build=i686-pc-cygwin --host=i686-pc-cygwin --target=i686-pc-cygwin
--cache-f
ile=../../.././config.cache
--srcdir=/usr/src/insight+dejagnu-20030520/dejagnu/example/calc
loading cache ../../.././config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
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

Per the procedure above, I'm clearly not building within my source tree, as
someone else on the list pointed out at one point.  Any idea what in the
world is going on here?  I'm ultimately trying to build a cross-debugger,
but the above happens even in native mode!  I've successfully built the
5.3.0 tree, but I can't use that because of the Tcl/Tk instabilities.

TIA...