From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eli Zaretskii" To: fnasser@cygnus.com Cc: gdb@sources.redhat.com, fche@cygnus.com Subject: Re: RFC: Change to gdb/README Date: Fri, 22 Dec 2000 01:22:00 -0000 Message-id: <3405-Fri22Dec2000112140+0200-eliz@is.elta.co.il> References: <3A3A8368.1AB607D@cygnus.com> <4839-Sat16Dec2000004058+0200-eliz@is.elta.co.il> <3A423C88.6C2402C6@cygnus.com> X-SW-Source: 2000-12/msg00129.html > Date: Thu, 21 Dec 2000 17:23:20 +0000 > From: Fernando Nasser > > I believe I have addressed Eli and Frank comments. Here it is: > > --------- > You can build GDB right in the source directory: > > cd gdb-5.0 > ./configure > make > cp gdb/gdb /usr/local/bin/gdb (or wherever you want) > > However, we recommend that an empty directory be used instead. > This way you do not clutter your source tree with binary files > and will be able to create different builds with different > configuration options. Thanks, this is fine with me. >From fnasser@cygnus.com Fri Dec 22 07:03:00 2000 From: Fernando Nasser To: Eli Zaretskii Cc: gdb@sources.redhat.com, fche@cygnus.com Subject: Re: RFC: Change to gdb/README Date: Fri, 22 Dec 2000 07:03:00 -0000 Message-id: <3A436CFC.CE0295F6@cygnus.com> References: <3A3A8368.1AB607D@cygnus.com> <4839-Sat16Dec2000004058+0200-eliz@is.elta.co.il> <3A423C88.6C2402C6@cygnus.com> <3405-Fri22Dec2000112140+0200-eliz@is.elta.co.il> X-SW-Source: 2000-12/msg00130.html Content-length: 825 It is in. Thank you. Eli Zaretskii wrote: > > > Date: Thu, 21 Dec 2000 17:23:20 +0000 > > From: Fernando Nasser > > > > I believe I have addressed Eli and Frank comments. Here it is: > > > > --------- > > You can build GDB right in the source directory: > > > > cd gdb-5.0 > > ./configure > > make > > cp gdb/gdb /usr/local/bin/gdb (or wherever you want) > > > > However, we recommend that an empty directory be used instead. > > This way you do not clutter your source tree with binary files > > and will be able to create different builds with different > > configuration options. > > Thanks, this is fine with me. -- Fernando Nasser Red Hat Canada Ltd. E-Mail: fnasser@redhat.com 2323 Yonge Street, Suite #300 Toronto, Ontario M4P 2C9 >From cgf@redhat.com Fri Dec 22 08:14:00 2000 From: Christopher Faylor To: gdb@sources.redhat.com Subject: [qqi@world.std.com: link update] Date: Fri, 22 Dec 2000 08:14:00 -0000 Message-id: <20001222111413.A11450@redhat.com> X-SW-Source: 2000-12/msg00131.html Content-length: 668 Who's maintaining the gdb web site these days? cgf ----- Forwarded message from Quality Quorum ----- From: Quality Quorum To: sourcemaster@sources.redhat.com Subject: link update Date: Fri, 22 Dec 2000 00:38:45 -0500 Hi, There are two links to my website from http://sources.redhat.com/gdb: http://www.std.com/qqi/labslave/rproxy.html http://www.std.com/qqi/ftp/protocol.txt They are moved to http://world.std.com/~qqi/labslave/rproxy.html http://world.std.com/~qqi/download/protocol.txt Please, update your links and let me know, I am going to remove old site. Thanks, Aleksey ----- End forwarded message ----- >From benoit.millot@cstelecom.com Tue Dec 26 06:53:00 2000 From: "Benoit MILLOT" To: ac131313 , "geoffk@cygnus.com" , ML GDB , ramasubr@aae.uiuc.edu Subject: Pb in making GDB5.0 --host=sparc-sun-solaris2.6 --target=ppc-eabi Date: Tue, 26 Dec 2000 06:53:00 -0000 Message-id: <3A48B202.A5806EC@cstelecom.com> X-SW-Source: 2000-12/msg00132.html Content-length: 1525 Hello, I'm working on host sparc-sun-solaris2.6 with gcc2.8.1 and DDD3.2.1 (GDB-5.0). I have already built on sparc for target=ppc-eabi and it work fine. But now using the same archive, during making an error occurs like that: gcc -c -g -O2 -DDEFAULT_INLINE=INLINE_LOCALS -DWITH_HOST_BYTE_ORDER=BIG_ENDIAN -DWITH_SMP=5 -DHAVE_TERMIOS_STRUCTURE -DHAVE_DEVZERO -I. -I../../../gdb+dejagnu-20001226/sim/ppc -I../../../gdb+dejagnu-20001226/sim/ppc/../../include -I../../bfd -I../../../gdb+dejagnu-20001226/sim/ppc/../../bfd -I../../gdb -I../../../gdb+dejagnu-20001226/sim/ppc/../../gdb -I../../../gdb+dejagnu-20001226/sim/ppc/../../gdb/config -I../../../gdb+dejagnu-20001226/sim/ppc/../../mmalloc semantics.c make: Fatal error: Don't know how to make target `../common/gentmap.c' Current working directory /home/millot/develop/gdbdev/essai/sim/ppc *** Error code 1 make: Fatal error: Command failed for target `all' Current working directory /home/millot/develop/gdbdev/essai/sim *** Error code 1 make: Fatal error: Command failed for target `all-sim' I don't know if tool had changed but according the diff between the old built archive and a new one (config.status config.cache), it seems to be same. So i have took the archive gdb+dejagnu-20001226 and the same errors occurs. Moreover, this error seems to be similar to http://sources.redhat.com/ml/gdb/2000-12/msg00113.html So I'd like to known if one tool is broken and which? or how do I correct this. Thanks a lot . Benoît >From pedwards@disaster.jaj.com Tue Dec 26 12:52:00 2000 From: Phil Edwards To: gdb@sources.redhat.com Subject: bad demangling, strange line numbers, caused by...? Date: Tue, 26 Dec 2000 12:52:00 -0000 Message-id: <20001226160130.A8025@disaster.jaj.com> X-SW-Source: 2000-12/msg00133.html Content-length: 1516 Using current CVS gdb to debug some code built with current CVS g++. (The code is a varation on "hello world" meant to point out some redirecting bugs in the library; it's nothing wacky.) Trying to step into a function gives me undemangled symbols (I thought that the autodetection was on now?), and then an "out of range" line number which I've never seen before. Pressing Enter (marked as below) still gets me into that function correctly, however. (gdb) n 8 std::cout << "Hello, Filesystem World!" << std::endl; (gdb) s _ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5Kc (__out=@0x21058, __s=0x10d68 "Hello, Filesystem World!") at std_ostream.h:635 Line number 635 out of range; std_ostream.h has 288 lines. (gdb) _ZNSo6sentryC1ERSo (this=0xffbef848, __os=@0x21058) at ostream.tcc:39 39 : _M_ok(__os.good()), _M_os(__os) (gdb) std_ostream.h does an #include of ostream.tcc; both files are mentioned above. The line numbers are way way off for ostream.tcc though. I suspect that's a compiler problem, but walking through other header files which do the same thing hasn't been a problem with this build. If I can get the demangling thing beat, that'd be nice. Anybody know what's doing this? Phil -- pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com devphil at several other less interesting addresses in various dot domains The gods do not protect fools. Fools are protected by more capable fools. >From dberlin@redhat.com Tue Dec 26 13:19:00 2000 From: Daniel Berlin To: Phil Edwards Cc: gdb@sources.redhat.com Subject: Re: bad demangling, strange line numbers, caused by...? Date: Tue, 26 Dec 2000 13:19:00 -0000 Message-id: References: <20001226160130.A8025@disaster.jaj.com> X-SW-Source: 2000-12/msg00134.html Content-length: 708 On Tue, 26 Dec 2000, Phil Edwards wrote: > > Using current CVS gdb to debug some code built with current CVS g++. > (The code is a varation on "hello world" meant to point out some redirecting > bugs in the library; it's nothing wacky.) > > Trying to step into a function gives me undemangled symbols (I thought that > the autodetection was on now?), No, nobody with the power over the right files has approved the change jason made, for some reason. Unless someone objects, i'll approve it, and take responsibility since it's a very small change, and I can say it falls under the obvious bugfix rule, as far as I am concerned (I'm not just pulling this out of thin air, I really feel it does). --Dan