From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dave Arnold" To: "Jim Ingham" , Subject: Re: Insight Actually work or is it just an alpha orpre-alpha? Date: Wed, 05 Jul 2000 18:41:00 -0000 Message-id: <025b01bfe6ec$88be33a0$64251004@homepc.freedsl.com> X-SW-Source: 2000-q3/msg00016.html hi Jim, how do I figure out the cygwin version. I was looking in the cygcheck output but didn't see it. is there another way? I'm sort of interested in doing the "build the .exe's yourself" way of doing things. I think it would be pretty good experience for me. I've built one gnu utility which had a configure script and it was pretty cool. I'd like to step it up and learn more about this and also get a Insight working with my cygwin install. So how exactly does cygwin build itself? does make first output builds to a temp directory and then you run install to update your cygwin installation? Does the "snapshot" of cygwin come with all the configure,makefile,source, etc needed to build it? I'm wondering because I had the impression that the snapshots give you only what you choose and you might not realize you're missing something until after you try to build, or do they package/group the snapshots up pretty good to make it simpler for us? Only other thing is how do you backout a bad install? does the "install.exe" utility have a way to "uninstall"? Sorry for the sudden burst of questions. thanks, /dave -----Original Message----- From: Jim Ingham To: Dave Arnold ; Dave Arnold ; insight@sourceware.cygnus.com Date: Wednesday, July 05, 2000 6:19 PM Subject: Re: Does Insight Actually work or is it just an alpha orpre-alpha? >Also sprach Dave Arnold: > >> hi Jim, >> >> 1. >> I did use "-g" option for gcc. > >Yeah, sorry to have to ask, but you never know... > >> >> 2. Version information: >> >> BASH.EXE-2.04$ bash --version >> GNU bash, version 2.04.0(1)-release (i586-pc-cygwin) >> Copyright 1999 Free Software Foundation, Inc. >> >> BASH.EXE-2.04$ gcc -v >> Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/specs >> gcc version 2.95.2 19991024 (release-2) >> >> BASH.EXE-2.04$ gdb -v >> GNU gdb 5.0 >> Copyright 2000 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". >> BASH.EXE-2.04$ >> >> 3. Other worse problems occur using gdb -nw >> like hanging bash window, can't find libccrt0.c, can't find source, etc. >> >> BASH.EXE-2.04$ gdb -nw load >> GNU gdb 5.0 >> Copyright 2000 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) list >> 1 /cygnus/netrel/src/cygwin-1.1.2/winsup/cygwin/libccrt0.cc: No such >> file >> or directory. >> (gdb) >> >> (gdb) list load5.c:1 >> No source file named load5.c. >> (gdb) list load5.c:main >> No source file named load5.c. >> (gdb) list >> 1 in /cygnus/netrel/src/cygwin-1.1.2/winsup/cygwin/libccrt0.cc >> (gdb) >> > >You do have one screwed up version of gdb, that is for sure... There may be >some conflict between the version of cygwin you are using and the one that >the gdb you got was build with? I think that the cygcheck command will tell >you your cygwin version. Don't know how you find out the version gdb was >built against. > >If you can't sort this out, you will probably need to have a stab at >building it yourself. For this you will need to get a recent (snapshot) >version of Cygwin, and the CVS version of insight (there were some problems >with the gdb 5.0 release vrs. Cygwin that you can find discussed on the >archives of this mailing list.) > >Then configure & make should give you what you want. Slight emphasis on the >"should". > >If you have more questions on the process of building, you should probably >address them to the cygwin mailing list (also on the sourceware.cygnus.com >site), not because we want to palm you off on someone else, but because that >is where the real experts on cygwin hide out... > >> >> THANKS FOR TAKING THE TIME TO HELP, > >Not a prob... > >Jim > >> /Dave >> >> -----Original Message----- >> From: Jim Ingham >> To: Dave Arnold ; insight@sourceware.cygnus.com >> >> Date: Wednesday, July 05, 2000 11:18 AM >> Subject: Re: Does Insight Actually work or is it just an alpha orpre-alpha? >> >> >>> Also sprach Dave Arnold: >>> >>> I have not tried Insight on Win95, only on NT, but some of Cygnus's >>> customers use it on 95, and it does seem to work. Couple of questions for >>> you come to mind: >>> >>> 1) How did you compile the code that you are trying to debug (presumably >>> gcc, but looks like not "-g"?) >>> >>> 2) What version of Cygwin are you using? >>> >>> 3) If you run "gdb -nw" do you get the same problems (does "list" show you >>> sources, do breakpoints work, etc...) >>> >>> Jim >>> >>>> has anyone actually been able to use Insight to do debugging? >>>> >>>> I have downloaded the latest and greatest pre-built version for windows95 >>>> and haven't been able to use it at all. Nice GUI but useless because >>>> >>>> 1. Breakpoints don't work >>>> 2. Can't load .exe's for debugging >>>> 3. Show's all source in Assembly. >>>> 4. Execution stops with error 193: >>>> 5. Single stepping doesn't work >>>> >>>> Let me elaborate: >>>> >>>> 1. Breakpoints don't work: >>>> >>>> run gdb from a bash prompt with executable name as argument: >> BASH.EXE-2.04$ >>>> gdb foo >>>> ...Insight gui pops up showing source code foo.c ... set a break point >> in >>>> main at the first >>>> instruction,...click run, then nothing happens, execution doesn't stop at >>>> the breakpoint, >>>> focus moves to last line of main() being highlighted and the red >> breakpoint >>>> marker there being >>>> on. >>>> >>>> 2. Can't load .exe's for debugging: >>>> ...run gdb like so: BASH.EXE-2.04$ gdb >>>> ...gui pops up...from file menu choose Open...browse to and choose an >>>> executable to debug... >>>> source is all displayed in assembly, cannot switch view to 'source' the >> file >>>> list at bottom >>>> of the window has bunch of files not associated with your program >>>> like...libccrt0.cc, mount.h, _ansi.h... >>>> and so on. Execution will stop at a breakpoint, but when trying to >> single >>>> step, program seems to >>>> run to completion and doesn't stop at the next instruction. >>>> >>>> 3. Source code in Assembly: >>>> ...when loading .exe's from commandline like so: gdb foo source code is >>>> shown C but when loading >>>> from file->open menu only viewable in assembly. >>>> >>>> 4. Execution stops with error 193: >>>> load an executable into gdb for debugging, >>>> open the console view >>>> (gdb) file foo >>>> (gdb) break main >>>> Breakpoint 3 at 0x2704: file foo.c, line 50. >>>> (gdb) r >>>> Starting program: /lab5/foo model1 >>>> Error: Error creating process /lab5/foo , (error 193) >>>> >>>> >>>> 5. Single stepping doesn't work: >>>> >>>> ...Same as above, can't step into a program. Have to set a breakpoint >> first >>>> I assume and then >>>> run...but I think this is just the way gdb works right? In order to step >> you >>>> have to first 'run' the program. >>>> but would be nice if you could step into a program without having to set >> any >>>> breakpoints. >>>> Sometimes what happens is the execution breaks in one of the cygwin files >>>> and Insight window is >>>> showing source like this: >>>> >>>> - 0x40374f : >>>> - 0x403754 : >>>> >>>> >>>> I would really like to use Insight to do debugging but so far it's >> useless >>>> to me besides having a nice >>>> GUI. Can anyone give me any suggestions to resolve these issues? >> Initially >>>> I was very excited to see >>>> such a great looking front end but that is starting to fade unless I >> figure >>>> out how to make this thing work. >>>> The online help is so minimal, doesn't help much. >>>> >>>> /dAVe >>>> >>>> >>>> >>> >>> -- >>> Jim Ingham jingham@apple.com >>> Apple Computer >>> >> > >-- >Jim Ingham jingham@apple.com >Apple Computer >