Re: Deprecated bfd_read warnings in the gdb(1)

2002-02-26 Thread Maxim Sobolev

Mark Peek wrote:
 
 At 9:34 AM -0800 2/25/02, David O'Brien wrote:
 On Mon, Feb 25, 2002 at 11:51:54AM +0200, Maxim Sobolev wrote:
I've noticed that after a recent make world gdb started producing
   warnings during startup. Please fix.
 
 Please send patch.  This will require gdb to be updated to GDB 5.1.1 --
 something I am not going to do.  This also shows the problems with trying
 to share libiberty across multiple software packages.
 
 Upgrading to gdb 5.1.1 *is* something that I am doing. In fact, I was
 testing kernel debugging over the weekend. However, the calls to
 bfd_read are still in gdb 5.1.1 so I could either patch it or wait
 for gdb 5.2 to be released. Of course, a simple patch to bfd.h could
 remove the warning as well...

That would be nice. We are waiting for it.

 If the warning is annoying people, I can make the patch to gdb. If it
 is tolerable, then let's wait for gdb 5.2.

I thinks that warnings shoud be disabled in any case, because they do
not serve any meaningful purpose, but only scaring newcomers and
annoying people like me.

Thanks!

-Maxim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Deprecated bfd_read warnings in the gdb(1)

2002-02-25 Thread Maxim Sobolev

David,

I've noticed that after a recent make world gdb started producing
warnings during startup. Please fix.

-Maxim

max@notebook$ uname -a
FreeBSD notebook 5.0-CURRENT FreeBSD 5.0-CURRENT #4: Tue Feb 19
19:46:58 EET 200
2 root@notebook:/usr/src/sys/i386/compile/NOTEBOOK  i386
max@notebook$ gdb mkdir
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...Deprecated
bfd_read called a
t
/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/dbxread.c
li
ne 2629 in elfstab_build_psymtabs
Deprecated bfd_read called at
/usr/src/gnu/usr.bin/binutils/gdb/../../../../cont
rib/gdb.291/gdb/dbxread.c line 935 in fill_symbuf

Breakpoint 1 at 0x804848d: file mkdir.c, line 137.

Breakpoint 1, build (path=0xbfbff958 //usr/local, omode=49087) at
mkdir.c:137
137 {
(gdb)

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Deprecated bfd_read warnings in the gdb(1)

2002-02-25 Thread David O'Brien

On Mon, Feb 25, 2002 at 11:51:54AM +0200, Maxim Sobolev wrote:
 David,
 
 I've noticed that after a recent make world gdb started producing
 warnings during startup. Please fix.

Please send patch.  This will require gdb to be updated to GDB 5.1.1 --
something I am not going to do.  This also shows the problems with trying
to share libiberty across multiple software packages.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Deprecated bfd_read warnings in the gdb(1)

2002-02-25 Thread Mark Peek

At 9:34 AM -0800 2/25/02, David O'Brien wrote:
On Mon, Feb 25, 2002 at 11:51:54AM +0200, Maxim Sobolev wrote:
   I've noticed that after a recent make world gdb started producing
  warnings during startup. Please fix.

Please send patch.  This will require gdb to be updated to GDB 5.1.1 --
something I am not going to do.  This also shows the problems with trying
to share libiberty across multiple software packages.

Upgrading to gdb 5.1.1 *is* something that I am doing. In fact, I was 
testing kernel debugging over the weekend. However, the calls to 
bfd_read are still in gdb 5.1.1 so I could either patch it or wait 
for gdb 5.2 to be released. Of course, a simple patch to bfd.h could 
remove the warning as well...

If the warning is annoying people, I can make the patch to gdb. If it 
is tolerable, then let's wait for gdb 5.2.

Mark

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message