Re: gdb breaks world
At 10:54 AM -0700 5/27/02, David O'Brien wrote: >Verify that your entire kernel is built with "-g -gstabs+". If you still >cannot use gdb on a core dump, maybe there is a core dump format change >GDB needs to catch up with. Please use the various objdump, etc. tools >to verify what type of debugging is in kernel.debug. I merged some of the gdb src/ code into the devel/gdb52 port to allow it to debug i386 kernels (without the -gstabs+ compile option). The replacement port can be found here: http://people.FreeBSD.org/~mp/gdb52.tar.gz I'd appreciate feedback prior to committing it. Thanks, Mark To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On Mon, May 27, 2002 at 04:08:44PM +0900, Jun Kuriyama wrote: > At Mon, 27 May 2002 02:46:01 + (UTC), > David O'Brien wrote: > > Add it to COPTFLAGS. Why are you adding it to DEBUG? > > ``grep DEBUG /sys/conf/*.mk /sys/conf/Makefile.*'' shows DEBUG is not > > used this way. > > I added it to DEBUG because I think "-gstabs+" will be used as > replacement of "-g". I added it to COPTFLAGS and tried again, but no > luck. > > makeoptions COPTFLAGS=-gstabs+ #Build kernel with gdb(1) debug symbols Verify that your entire kernel is built with "-g -gstabs+". If you still cannot use gdb on a core dump, maybe there is a core dump format change GDB needs to catch up with. Please use the various objdump, etc. tools to verify what type of debugging is in kernel.debug. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
At Mon, 27 May 2002 02:46:01 + (UTC), David O'Brien wrote: > Add it to COPTFLAGS. Why are you adding it to DEBUG? > ``grep DEBUG /sys/conf/*.mk /sys/conf/Makefile.*'' shows DEBUG is not > used this way. I added it to DEBUG because I think "-gstabs+" will be used as replacement of "-g". I added it to COPTFLAGS and tried again, but no luck. makeoptions COPTFLAGS=-gstabs+ #Build kernel with gdb(1) debug symbols (gdb) core-file /var/crash/vmcore.6 "/var/crash/vmcore.6" is not a core dump: File format not recognized Sorry for my silly questions... -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On Mon, May 27, 2002 at 11:12:47AM +0900, Jun Kuriyama wrote: > At Wed, 22 May 2002 18:54:02 + (UTC), > David O'Brien wrote: > > -ggdb means to use the most "expressive" debugging format the compiler > > knows about. You want -gstabs+ or -gstabs > > I cannot debug a kernel with -gstabs+ option. Any hints about this? > > % cd sys/i386/compile/WATERBLUE > % grep gdb ../../conf/WATERBLUE > makeoptions DEBUG=-gstabs+ #Build kernel with gdb(1) debug symbols Add it to COPTFLAGS. Why are you adding it to DEBUG? ``grep DEBUG /sys/conf/*.mk /sys/conf/Makefile.*'' shows DEBUG is not used this way. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
At Sun, 26 May 2002 21:35:28 -0500, David W. Chapman Jr. <[EMAIL PROTECTED]> wrote: > > % sudo gdb52 > Last time I checked, gdb was broken in -current and people were > encouraged to use gdb in the ports system, but this may be oudated. Yes, I'm using gdb52 from ports/devel/gdb52. -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On Mon, May 27, 2002 at 11:12:47AM +0900, Jun Kuriyama wrote: > At Wed, 22 May 2002 18:54:02 + (UTC), > David O'Brien wrote: > > -ggdb means to use the most "expressive" debugging format the compiler > > knows about. You want -gstabs+ or -gstabs > > I cannot debug a kernel with -gstabs+ option. Any hints about this? > > % cd sys/i386/compile/WATERBLUE > % grep gdb ../../conf/WATERBLUE > makeoptions DEBUG=-gstabs+ #Build kernel with gdb(1) debug symbols > % sudo gdb52 > (gdb) symbol-file kernel.debug > Reading symbols from kernel.debug...done. > (gdb) exec-file kernel > (gdb) core-file /var/crash/vmcore.4 > "/var/crash/vmcore.4" is not a core dump: File format not recognized > Last time I checked, gdb was broken in -current and people were encouraged to use gdb in the ports system, but this may be oudated. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
At Wed, 22 May 2002 18:54:02 + (UTC), David O'Brien wrote: > -ggdb means to use the most "expressive" debugging format the compiler > knows about. You want -gstabs+ or -gstabs I cannot debug a kernel with -gstabs+ option. Any hints about this? % cd sys/i386/compile/WATERBLUE % grep gdb ../../conf/WATERBLUE makeoptions DEBUG=-gstabs+ #Build kernel with gdb(1) debug symbols % sudo gdb52 (gdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (gdb) exec-file kernel (gdb) core-file /var/crash/vmcore.4 "/var/crash/vmcore.4" is not a core dump: File format not recognized -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On Wed, May 22, 2002 at 09:57:24AM +0100, Doug Rabson wrote: > On Monday 20 May 2002 3:49 am, Terry Lambert wrote: > > Steve Kargl wrote: > > > > Use "-ggdb" instead, thus avoiding DWARF. > > > > > > BZZZT... Thanks for play! -ggdb means to use the most "expressive" debugging format the compiler knows about. You want -gstabs+ or -gstabs To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On Wednesday 22 May 2002 6:49 pm, David O'Brien wrote: > On Wed, May 22, 2002 at 09:57:24AM +0100, Doug Rabson wrote: > > GDB 5.2 works pretty well with -current - I've been using it recently. I > > plan to upgrade GDB in -current to 5.2 soon (as soon as David has enough > > time to sort out the CVS magic). > > I fail to see your patches to gdb 5.2 for the kernel bits. > It would be nice to get them in the public view before they are > committed. I'll certainly put them up for review when I've written them. I've been busy on other things since we last spoke on the subject. -- Doug Rabson Mail: [EMAIL PROTECTED] Phone: +44 20 8348 6160 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On Wed, May 22, 2002 at 09:57:24AM +0100, Doug Rabson wrote: > GDB 5.2 works pretty well with -current - I've been using it recently. I plan > to upgrade GDB in -current to 5.2 soon (as soon as David has enough time to > sort out the CVS magic). I fail to see your patches to gdb 5.2 for the kernel bits. It would be nice to get them in the public view before they are committed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On Monday 20 May 2002 3:49 am, Terry Lambert wrote: > Steve Kargl wrote: > > > Use "-ggdb" instead, thus avoiding DWARF. > > > > BZZZT... Thanks for play! > > Did Mark Peek's suggestion of using the gdb that matched > the compiler (gdb 5.2 from ports) work instead? GDB 5.2 works pretty well with -current - I've been using it recently. I plan to upgrade GDB in -current to 5.2 soon (as soon as David has enough time to sort out the CVS magic). -- Doug Rabson Mail: [EMAIL PROTECTED] Phone: +44 20 8348 6160 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
Steve Kargl wrote: > > Use "-ggdb" instead, thus avoiding DWARF. > > BZZZT... Thanks for play! Did Mark Peek's suggestion of using the gdb that matched the compiler (gdb 5.2 from ports) work instead? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On Sun, May 19, 2002 at 05:50:32PM -0700, Terry Lambert wrote: > > > Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. > > Use "-ggdb" instead, thus avoiding DWARF. > BZZZT... Thanks for play! kargl[204] gcc -ggdb a.c kargl[205] gdb a.out GNU gdb 4.18 Copyright 1998 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 "i386-unknown-freebsd"... Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
Steve Kargl wrote: > Finally, since you're quick with the wit, can you tell me > how to debug the following problem when I can't compile > the debugger. [ ... ] > gcc -g a.c [ ... ] > Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. Use "-ggdb" instead, thus avoiding DWARF. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On 2002-05-19 17:00, Matthew Dillon wrote: > > :> You know, every time I update my -current sources it's winding up > :> taking me an entire day to get things to build again. > : > :There are cases where updating with the `new files' requires that you > :have updated to the `new files', aka chicken and egg problems. This > :is true with the -DNO_WERROR thing, in my opinion. Let's not blame > :David O'Brien for anything, since he's doing such a huge amount of > :work already :/ > : > :After all, this is -CURRENT. > :It's not even guaranteed to work at all times ;-) > : > :- Giorgos > > It's just that it gets frustrating. If there were only one problem > with the build then, sure, no big deal. But between the filesystem > import, compiler upgrade, and the warnings failures it has taken all > day for me just to get to the point where it is now dying on Greg's > doc commit. And when we get past that problem will another hit us? > I'll probably wind up having to build the world a dozen times before I > get something I can install. I know the feeling, I haven't been ablt to build world on this slow machine of mine for ages. This is why I'm still running on a 5.x build of late April :-/ % uname -v FreeBSD 5.0-CURRENT #1: Thu Apr 25 01:11:09 EEST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GALADRIEL But whatever. I can still test most of the work I'm doing, being mostly interested in manpages and SGML docs. You have a point though, no objections from here. CURRENT is approaching the -RELEASE of November every day, and is still somewhat fragile for me ;) -- Giorgos Keramidas- http://www.FreeBSD.org [EMAIL PROTECTED] - The Power to Serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
:> You know, every time I update my -current sources it's winding up :> taking me an entire day to get things to build again. : :There are cases where updating with the `new files' requires that you :have updated to the `new files', aka chicken and egg problems. This :is true with the -DNO_WERROR thing, in my opinion. Let's not blame :David O'Brien for anything, since he's doing such a huge amount of :work already :/ : :After all, this is -CURRENT. :It's not even guaranteed to work at all times ;-) : :- Giorgos It's just that it gets frustrating. If there were only one problem with the build then, sure, no big deal. But between the filesystem import, compiler upgrade, and the warnings failures it has taken all day for me just to get to the point where it is now dying on Greg's doc commit. And when we get past that problem will another hit us? I'll probably wind up having to build the world a dozen times before I get something I can install. Throw in ipfw changes and the fact that procfs does not work with the old mount binary and it's taken quite a bit of munging to just be able to build, install, and run a new kernel, let alone the world. I'm going to try make -k next but I don't have high hopes. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On 2002-05-19 13:31, Matthew Dillon wrote: > David O'Brien wrote: >: >:Because we are wanting for people to let the dust settle on the switch to >:GCC 3.1. It is best for people to juse use -DNO_WERROR for now. >:Patience. > > Ahhh.. so *that's* why everything broke when I did a full update. > > You know, every time I update my -current sources it's winding up > taking me an entire day to get things to build again. There are cases where updating with the `new files' requires that you have updated to the `new files', aka chicken and egg problems. This is true with the -DNO_WERROR thing, in my opinion. Let's not blame David O'Brien for anything, since he's doing such a huge amount of work already :/ After all, this is -CURRENT. It's not even guaranteed to work at all times ;-) - Giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
At 2:58 PM -0700 5/19/02, Steve Kargl wrote:
>Finally, since you're quick with the wit, can you tell me
>how to debug the following problem when I can't compile
>the debugger.
>
>kargl[223] cat a.c
>#include
>int main(void) {
>/* This isn't the problem. The problem is with gdb. */
>abort();
>}
>kargl[224] !gcc
>gcc -g a.c
>kargl[225] gdb a.out
>GNU gdb 4.18
>Copyright 1998 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 "i386-unknown-freebsd"...
>
>Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.
This appears to be due to the switch to gcc-3.1. A bug has been filed
in gnats on this problem (bin/38236: gdb do not work with gcc-3.1).
For now, the workaround is to use the devel/gdb52 port.
Mark
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On Sun, May 19, 2002 at 02:19:27PM -0700, Terry Lambert wrote:
> Both Twins: "Wonder Twin powers, Activate!"
>
> Jayna:"Take the form of ... patches!"
> Zan: "Take the form of ... a complaining email!"
> Gleek the code monkey:"Gleek! Gleek! Gleek!"
>
Terry, you are an idiot. I wasn't complaining! I hadn't
seen this particular failure mentioned on the list. David
was probably aware of the problem, but in case he (and others)
hadn't seen the problem, I reported it in a short email with
the details.
If I were to complain, I'd choose the lack of functional
C++ libraries after the gcc 3.1 upgrade. I, however,
recognize the difficult and thankless job that David has
with maintaining the compiler infrastructure.
Finally, since you're quick with the wit, can you tell me
how to debug the following problem when I can't compile
the debugger.
kargl[223] cat a.c
#include
int main(void) {
/* This isn't the problem. The problem is with gdb. */
abort();
}
kargl[224] !gcc
gcc -g a.c
kargl[225] gdb a.out
GNU gdb 4.18
Copyright 1998 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 "i386-unknown-freebsd"...
Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
David O'Brien wrote: > > > Warnings are treated as errors. Since GCC 3.1 has brought a hell of a > > > lot more warnings with us, you should use -DNO_WERROR until the dust > > > of the GCC 3.1 import settles down. > > > > If everyone is using -DNO_WERROR, then who would report build > > problems :-). > > Because we are wanting for people to let the dust settle on the switch to > GCC 3.1. It is best for people to juse use -DNO_WERROR for now. > Patience. Both Twins: "Wonder Twin powers, Activate!" Jayna: "Take the form of ... patches!" Zan:"Take the form of ... a complaining email!" Gleek the code monkey: "Gleek! Gleek! Gleek!" [ ... meanwhile, in the cartoon viewers' cave ... ] Bob:"That second Wonder Twin really has an incredibly lame power!" Tom:"Pass the potato chips!" [ ... http://www.seanbaby.com/superfriends/wondertwins.htm ; hit the "back" circle for the rest of the Super Friends. 8-) ... ] -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
:> > lot more warnings with us, you should use -DNO_WERROR until the dust :> > of the GCC 3.1 import settles down. :> :> If everyone is using -DNO_WERROR, then who would report build :> problems :-). : :Because we are wanting for people to let the dust settle on the switch to :GCC 3.1. It is best for people to juse use -DNO_WERROR for now. :Patience. : Ahhh.. so *that's* why everything broke when I did a full update. You know, every time I update my -current sources it's winding up taking me an entire day to get things to build again. This is the third time that's happened. I have spent at least 5 hours building the world and the kernel over and over again to try to produce a bootable system. The annoyance factor is quite high. It would be more considerate of comitters if they would adjust the defaults for these things so at the very least one can buildworld or buildkernel without having to do something special. It may be best for *you* not to spend the time, but look at the huge amount of other people's time that is being wasted by these little snafus! I do appreciate all the compiler tools work, I know it isn't easy. I'm just asking that a little more care be taken in regards to the other developers trying to work with -current (which is more and more these days). Don't expose breakage to the whole development community on purpose! -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On Sat, May 18, 2002 at 08:12:15PM -0700, Steve Kargl wrote: > > Warnings are treated as errors. Since GCC 3.1 has brought a hell of a > > lot more warnings with us, you should use -DNO_WERROR until the dust > > of the GCC 3.1 import settles down. > > If everyone is using -DNO_WERROR, then who would report build > problems :-). Because we are wanting for people to let the dust settle on the switch to GCC 3.1. It is best for people to juse use -DNO_WERROR for now. Patience. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On 2002-05-18 20:12, Steve Kargl wrote: > On Sun, May 19, 2002 at 05:31:08AM +0300, Giorgos Keramidas wrote: > > Warnings are treated as errors. Since GCC 3.1 has brought a hell > > of a lot more warnings with us, you should use -DNO_WERROR until > > the dust of the GCC 3.1 import settles down. > > If everyone is using -DNO_WERROR, then who would report build > problems :-). True. I mentioned -DNO_WERROR to help you complete the buildworld. If you can help with those warnings, then I'm sure David O'Brien will be very glad to see patches ;-) -- Giorgos Keramidas- http://www.FreeBSD.org [EMAIL PROTECTED] - The Power to Serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On Sun, May 19, 2002 at 05:31:08AM +0300, Giorgos Keramidas wrote: > On 2002-05-18 12:56, Steve Kargl wrote: > > ===> gnu/usr.bin/binutils/gdb > > cc -O -pipe -march=athlon -D_GNU_SOURCE -I. >-I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb >-I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include >-Dprint_insn_i386=print_insn_i386_att -Dprint_insn_i386=print_insn_i386_att >-I/usr/src/gnu/usr.bin/binutils/gdb/i386 >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config >-DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb >-I/usr/obj/usr/src/i386/usr/include/readline -Werror -Wall -Wno-format-y2k -W >-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c init.c > > cc1: warnings being treated as errors > > Known problem. I read this list everyday. I did not recall seeing this particular failure mentioned, so I thought I'd report it. > Warnings are treated as errors. Since GCC 3.1 has brought a hell of a > lot more warnings with us, you should use -DNO_WERROR until the dust > of the GCC 3.1 import settles down. If everyone is using -DNO_WERROR, then who would report build problems :-). -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gdb breaks world
On 2002-05-18 12:56, Steve Kargl wrote: > ===> gnu/usr.bin/binutils/gdb > cc -O -pipe -march=athlon -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 >-I/usr/src/gnu/usr.bin/binutils/gdb >-I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include >-Dprint_insn_i386=print_insn_i386_att -Dprint_insn_i386=print_insn_i386_att >-I/usr/src/gnu/usr.bin/binutils/gdb/i386 >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb >-I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config >-DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb >-I/usr/obj/usr/src/i386/usr/include/readline -Werror -Wall -Wno-format-y2k -W >-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c init.c > cc1: warnings being treated as errors Known problem. Warnings are treated as errors. Since GCC 3.1 has brought a hell of a lot more warnings with us, you should use -DNO_WERROR until the dust of the GCC 3.1 import settles down. -- Giorgos Keramidas- http://www.FreeBSD.org [EMAIL PROTECTED] - The Power to Serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gdb breaks world
===> gnu/usr.bin/binutils/gdb cc -O -pipe -march=athlon -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -Dprint_insn_i386=print_insn_i386_att -Dprint_insn_i386=print_insn_i386_att -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config -DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/usr/include/readline -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c init.c cc1: warnings being treated as errors init.c:3: warning: function declaration isn't a prototype init.c: In function `initialize_all_files': init.c:4: warning: function declaration isn't a prototype init.c:5: warning: function declaration isn't a prototype init.c:6: warning: function declaration isn't a prototype init.c:7: warning: function declaration isn't a prototype init.c:8: warning: function declaration isn't a prototype init.c:9: warning: function declaration isn't a prototype init.c:10: warning: function declaration isn't a prototype init.c:11: warning: function declaration isn't a prototype init.c:12: warning: function declaration isn't a prototype init.c:13: warning: function declaration isn't a prototype skiping 51 more warnings init.c:64: warning: function declaration isn't a prototype *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/gdb. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
