4a24038b4c
when using gdb on a remote target. The fix is to restrict PT_GETDBREGS calls to `child' and `freebsd-uthreads' targets solely. I've been in some conversation with Brian about this, and this solution seems to be the most appropriate one. PR: gnu/21685 Submitted by: bsd |
||
---|---|---|
.. | ||
as | ||
awk | ||
bc | ||
binutils | ||
cc | ||
cpio | ||
cvs | ||
dc | ||
dialog | ||
diff | ||
diff3 | ||
gdb/doc | ||
gperf | ||
grep | ||
groff | ||
gzip | ||
ld | ||
man | ||
patch | ||
perl | ||
ptx | ||
rcs | ||
sdiff | ||
send-pr | ||
sort | ||
tar | ||
texinfo | ||
Makefile | ||
Makefile.inc |