Subject: Re: gdb acting up, anyone else seen this?
To: Andrew Brown <atatat@atatdot.net>
From: Bill Studenmund <wrstuden@netbsd.org>
List: tech-toolchain
Date: 04/08/2003 10:40:52
On Tue, 8 Apr 2003, Andrew Brown wrote:

> by way of introduction, let me say:
>
> NetBSD this 1.6Q NetBSD 1.6Q (THAT) #176: Sun Apr  6 01:47:26 EST 2003  andrew@this:/usr/src/sys/arch/i386/compile/THAT i386
>
> userland and kernel were built from sources last updated 20030325.
>
> gdb is dumping core and toasting binaries for me.  here are three
> quick back-to-back sessions with gdb.
>
> 	$ cp /netbsd k1
>
> 	$ gdb -write k1
> 	[...copyright omitted...]
> 	(gdb) print securelevel
> 	$1 = -1
> 	(gdb) set var securelevel=0
> 	(gdb) print securelevel
> 	$2 = 0
> 	(gdb) q
> 	[1]   Segmentation fault (core dumped) gdb -write k1
>
> 	$ gdb -write k1
> 	[...copyright omitted...]
> 	(gdb) print securelevel
> 	$1 = 0
> 	(gdb) q
>
> 	$ gdb -write k1
> 	[...copyright omitted...]
> 	(gdb) print securelevel
> 	No symbol table is loaded.  Use the "file" command.
> 	(gdb) q
>
> anyone else seeing this?  i'm certainly planning on updating again any
> day now...

Yes. I've seen it when I went changing rtc_offset. Was with recent libbfd
& gdb.

gdb on itself says:

(gdb) bt
#0  0x481d787d in _bfd_elf_strtab_emit () from /usr/lib/libbfd.so.5
#1  0x481dea05 in _bfd_elf_write_object_contents () from
/usr/lib/libbfd.so.5
#2  0x4820299e in bfd_close () from /usr/lib/libbfd.so.5
#3  0x80abe02 in dladdr ()
#4  0x80e6737 in dladdr ()
#5  0x80e6796 in dladdr ()
#6  0x8080036 in dladdr ()
#7  0x80803b0 in dladdr ()
#8  0x80ff92a in regfree ()
#9  0x807f9a3 in dladdr ()
#10 0x807ff5d in dladdr ()
#11 0x807f32e in dladdr ()
#12 0x807ee1b in dladdr ()
#13 0x807ee59 in dladdr ()
#14 0x80e38a0 in dladdr ()
#15 0x807ee8c in dladdr ()
#16 0x807fa82 in dladdr ()
#17 0x8103072 in regfree ()
#18 0x80e38a0 in dladdr ()
#19 0x8103c27 in regfree ()
#20 0x80e38a0 in dladdr ()
#21 0x8103c53 in regfree ()
#22 0x804b5a4 in free ()

Take care,

Bill