trying to unwind while unwinding; plus the sniffer is not allowed to unwind.
- Return the outer frame to terminate not the null frame.
This fixes the kernel track unwinder, so enable it.
When -Bsymbolic, all resolved symbols need to be created with relative
relocations. The dynamic linker depends on that because it only
knows how to perform relative relocations in the first pass to
relocate itself. This bug ended up creating R_SPARC_64 symbols for
12 relocation symbols in ld.elf_so, one of them dlopen(), which
ended up breaking things using dlopen(), most notably PAM.
for platforms with shlibs already (and are.)
this obsoletes our hacks for the libgcc specs to use libgcc_pic, and
fixes a couple of other issues reported to me directly.
targets. Use this function in the initiator, to ensure that the same limit
is used throughout (i.e. stop you attempting to compile the initiator with a
different limit to the library - the initiator uses the library for most of
its functionality).
If truncating the number of targets in the initiator, truncate it to the
correct amount, not half of what it should be.
Obey RFC3720 when determining targets. SendTargets=All MUST be supported
on a discovery session, and MUST NOT be supported on an operational session.
Previously, SendTargets=All was used both in the initial discovery session
and the later session. (from Daisuke Aoyama - author of istgt).
xsrc/external/mit/xkeyboard-config/dist/ directory, i.e.
- pull changes from xkeyboard-config 2.0 to 2.3
- put back entries for sharp machines (zaurus and hpcarm wzero3s)
removed in rev 1.4 (xkeyboard-config 2.0 merge)
XXX1: can't we generate these files during build?
XXX2: hpcarm W-ZERO3 keyboard on X still has some troubles...
gdb asserts when a frame returns 0. In previous versions of gdb, it just
printed 0, and stopped scanning. Our unwinder produces the same results in
both versions of gdb, i.e. it is broken and worse than the current gdb
default. We will need to revisit this for kernel debugging.
