From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hansjörg Petriffer To: "'gdb@sourceware.cygnus.com'" Subject: Problems with run tests on a i386 platform -Additional info Date: Fri, 23 Mar 2001 08:58:00 -0000 Message-id: X-SW-Source: 2001-03/msg00242.html Sorry in the last mail I have forgotten to give information about the used version and so on: -I use the insight release 5.0 -Cygwin 1.1.18 -Win2k I have the following problems with using gdb wiht a i386target (with ecos running). I'm not sure if I make something wrong. I receive the following messages: *** 16:13:51 Run started 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 "--host=i686-pc-cygwin --target=i386-elf"... (gdb) set height 0 (gdb) set remotedebug 0 Warning: command 'set remotedebug' is deprecated. Use 'set debug remote'. (gdb) set remotebaud 38400 (gdb) target remote com1 Remote debugging using com1 Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Couldn't establish connection to remote target Malformed response to offset query, timeout (gdb) load You can't do that when your target is `exec' (gdb) break cyg_test_exit Breakpoint 1 at 0x16cef: file //d/daten/source/ecos/source/packages/infra/v1_3_1/src/tcdiag.cxx, line 116. (gdb) break cyg_assert_fail Function "cyg_assert_fail" not defined. (gdb) break cyg_test_init Breakpoint 2 at 0x16c0b: file //d/daten/source/ecos/source/packages/infra/v1_3_1/src/tcdiag.cxx, line 62. (gdb) cont The program is not being run. (gdb) set cyg_test_is_simulator=0 Address of symbol "cyg_test_is_simulator" is unknown. (gdb) cont The program is not being run. (gdb) *** 16:15:09 Run complete *** 16:15:09 Run complete It seems for me that something goes wrong with the serial comunication, because it makes no difference if the remote is running. As serial cable I use a Simple null modem without handshaking. Is this correct? Thanks for any hint! Hansjoerg >From ac131313@cygnus.com Fri Mar 23 08:58:00 2001 From: Andrew Cagney To: Fernando Nasser Cc: gdb@sources.redhat.com Subject: Re: A nomination for testsuite co-maintainers Date: Fri, 23 Mar 2001 08:58:00 -0000 Message-id: <3ABAB247.1B84FB6B@cygnus.com> References: <3AB783A0.B3BDA9C1@redhat.com> X-SW-Source: 2001-03/msg00240.html Content-length: 1272 Fernando Nasser wrote: > testsuite Fernando Nasser fnasser@cygnus.com > config Mark Salter msalter@redhat.com > lib Mark Salter msalter@redhat.com > gdbtk Keith Seitz keiths@redhat.com > mi tests Elena Zannoni ezannoni@redhat.com > stabs tests Elena Zannoni ezannoni@redhat.com > threads Michael Snyder msnyder@redhat.com > trace Michael Snyder msnyder@redhat.com > hp tests (gdb.hp) (vacant) > Java tests (gdb.java) Anthony Green green@cygnus.com Sounds good. > P.S.: Just a clarification: I do not have the power to delegate in whole > of in part the maintainership (even of what I am maintainer of). This > is a nomination only, a suggestion for appreciation by the community, > and any of this will only be valid after Andrew gives the word for > people to add themselves to the MAINTAINERS file (the final part of our > maintainers "initiation"). No. I delegate. It is left to the community to object. However, I do appreciate being kept in the loop before people are approached. That should avoid me going ``doh!'' :-) Andrew >From ac131313@cygnus.com Fri Mar 23 08:58:00 2001 From: Andrew Cagney To: jtc@redback.com Cc: GDB Discussion Subject: Re: OBSOLETE GDB PowerPC LE platforms Date: Fri, 23 Mar 2001 08:58:00 -0000 Message-id: <3ABAA1BA.F0F7A6CA@cygnus.com> References: <3AB047E3.E52B9F8E@cygnus.com> <5mofv2u9ur.fsf@jtc.redback.com> X-SW-Source: 2001-03/msg00244.html Content-length: 96 > We should also consider removing: > powerpc-*-netware* What the heck. Done. Andrew >From cgf@redhat.com Fri Mar 23 08:58:00 2001 From: Christopher Faylor To: gdb@sources.redhat.com Subject: Sorry. Another test Date: Fri, 23 Mar 2001 08:58:00 -0000 Message-id: <20010323115909.A15237@redhat.com> X-SW-Source: 2001-03/msg00239.html Content-length: 62 This mailing list is stalled. I'm trying to restart it. cgf >From tanvir.hassan@tumisoftware.com Fri Mar 23 08:58:00 2001 From: Tanvir Hassan To: "'gdb@sourceware.cygnus.com'" Subject: using GDB 5 on Solaris 7 with Sun WS5.0 Date: Fri, 23 Mar 2001 08:58:00 -0000 Message-id: <3DD49A5C2322D411B6AE00C00D01611506CD71@HELIOS> X-SW-Source: 2001-03/msg00241.html Content-length: 1474 Hi All! I am using some 3rd party tools that have basically forced me to run SunWorkshop 5.0 on Solaris 7. When I try to use dbx to debug my app (~45Mb with -g) it crashes. I have applied all patches to dbx and it still crashes. So I have given up on it for now. Using GDB has exposed several issues: 1) they say I need to use "-g -xs" which when I use on all .o's in my app will make an 800Mb exe and is too ponderous to debug. I have heard that someone might have changed GDB to do "lazy" loading of symbols by reading them from the *.o instead of the exe and thus obviating the need for "-xs", but I don't see any mention of this in any of the source. If anyone knows about that Solaris fix, please let me know! 2) the name mangling/vtable scheme of Sun WS5.0 is apparently using the ISO/ANSI ABI standard and GDB cannot deal with it (it needs an new BFD to handle this? or is there a generic name de-mangling place in the code?), so now at least it is not crashing, but I cannot view any symbols. I tried to use the Sun compiler in -compat mode (and GDB DOES understand those mangled names), but then I cannot use STL (which is TOTALLY unacceptable). Is there a version of GDB out there that will work with the output of Sun WS5.0 CC (the C++ compiler and linker) on Solaris 7? Because the rest of my software is only certified (and thus only supported) on Solaris 7 with Sun WS5.0 I am stuck using that toolchain and cannot move to GCC (for now). Thanks! >From ac131313@cygnus.com Fri Mar 23 08:58:00 2001 From: Andrew Cagney To: jtc@redback.com Cc: GDB Discussion Subject: Re: OBSOLETE GDB m68k platforms Date: Fri, 23 Mar 2001 08:58:00 -0000 Message-id: <3ABAA130.90FB01AD@cygnus.com> References: <3AB03EF5.FBB5ACF8@cygnus.com> <5msnkeua35.fsf@jtc.redback.com> X-SW-Source: 2001-03/msg00243.html Content-length: 545 "J.T. Conklin" wrote: > > >>>>> "Andrew" == Andrew Cagney writes: > Andrew> As part of GDB 5.1, the following m68k platforms have been identified > Andrew> as candidates for obsolescence: > Andrew> > Andrew> m68*-isi-* > Andrew> m68*-sony-* > > We might also want to consider removing: > m68*-rom68k-* > m68*-*bug-* Hmm, added. The are marketing names. > These are other aliases that don't make sense today: > m68*-monitor-* > m68*-est-* Also added. thanks, Andrew >From hpetriffer@grips.com Fri Mar 23 09:09:00 2001 From: Hansjörg Petriffer To: "'gdb@sourceware.cygnus.com'" Subject: Problems with run tests on a i386 platform Date: Fri, 23 Mar 2001 09:09:00 -0000 Message-id: X-SW-Source: 2001-03/msg00246.html Content-length: 1852 I have the following problems with using gdb wiht a i386target (with ecos running). I'm not sure if I make something wrong. I receive the following messages: *** 16:13:51 Run started 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 "--host=i686-pc-cygwin --target=i386-elf"... (gdb) set height 0 (gdb) set remotedebug 0 Warning: command 'set remotedebug' is deprecated. Use 'set debug remote'. (gdb) set remotebaud 38400 (gdb) target remote com1 Remote debugging using com1 Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Couldn't establish connection to remote target Malformed response to offset query, timeout (gdb) load You can't do that when your target is `exec' (gdb) break cyg_test_exit Breakpoint 1 at 0x16cef: file //d/daten/source/ecos/source/packages/infra/v1_3_1/src/tcdiag.cxx, line 116. (gdb) break cyg_assert_fail Function "cyg_assert_fail" not defined. (gdb) break cyg_test_init Breakpoint 2 at 0x16c0b: file //d/daten/source/ecos/source/packages/infra/v1_3_1/src/tcdiag.cxx, line 62. (gdb) cont The program is not being run. (gdb) set cyg_test_is_simulator=0 Address of symbol "cyg_test_is_simulator" is unknown. (gdb) cont The program is not being run. (gdb) *** 16:15:09 Run complete *** 16:15:09 Run complete It seems for me that something goes wrong with the serial comunication, because it makes no difference if the remote is running. As serial cable I use a Simple null modem without handshaking. Is this correct? Thanks for any hint! Hansjoerg >From robert123@operamail.com Fri Mar 23 09:09:00 2001 From: To: gdb@sources.redhat.com Subject: Building insight on cygwin. Date: Fri, 23 Mar 2001 09:09:00 -0000 Message-id: <31fd6bda0f77a666e4c67cef522d6d81@NO-ID-FOUND.mhonarc.org> X-SW-Source: 2001-03/msg00247.html Content-length: 579 This may be obvious to everyone else but I missed it, To get insight+dejagnu-20010321 to build with gcc 2.95.3-1 on cygwin I needed to export 'CC=gcc -mwin32'. With that done I was able to build GDB for the sh-coff target. Here is the script I now use:- #Configure Insight: export 'CC=gcc -mwin32' mkdir -p /tmp/build/gdb cd /tmp/build/gdb/ /src/insight+dejagnu-20010321/configure --target=sh-coff \ --prefix=/sh-tools \ --exec-prefix=/sh-tools/sh-coff-2.95.2 \ -v 2>&1 | tee configure.out #Build and install Insight: make -w all install 2>&1 | tee make.out Robert.