tech-kern archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
re: ALTQ cannot be stopped Was: Fwd: 10-BETA : some network issues
> Reading symbols from /usr/libdata/debug//usr/lib/libm.so.0.12.debug...
> (No debugging symbols found in
> /usr/libdata/debug//usr/lib/libm.so.0.12.debug)
> Reading symbols from /usr/lib/libc.so.12...
> Reading symbols from /usr/libdata/debug//usr/lib/libc.so.12.220.debug...
> (No debugging symbols found in
> /usr/libdata/debug//usr/lib/libc.so.12.220.debug)
> Reading symbols from /usr/libexec/ld.elf_so...
> (No debugging symbols found in /usr/libexec/ld.elf_so)
> [Switching to LWP 7893 of process 7893]
> 0x000000010820564b in qop_clear ()
> (gdb) bt
> #0 0x000000010820564b in qop_clear ()
> #1 0x0000000108205774 in qop_delete_if ()
> #2 0x00000001082058c6 in qcmd_destroyall ()
> #3 0x0000000108212c45 in main ()
> (gdb) info locals
> No symbol table info available.
> (gdb)
>
> I don't understand why gdb complains about debugging symbols.
i think it's because our build has a bug. i was recently
trying to debug something in a shared library and had the
same problem and i traced it down to this code:
share/mk/bsd.README:MKSTRIPSYM If "yes", strip all local symbols from shared libraries;
share/mk/bsd.lib.mk:.if ${MKSTRIPSYM:Uyes} == "yes"
share/mk/bsd.lib.mk:_LIBLDOPTS+= -Wl,-x
share/mk/bsd.lib.mk:.else
share/mk/bsd.lib.mk:_LIBLDOPTS+= -Wl,-X
and putting "MKSTRIPSYM=no" in my mk.conf fixed it.
i believe this is a bug and should default to "no", if
MKDEBUG has also been enabled.
.mrg.
Home |
Main Index |
Thread Index |
Old Index