ptrace problem 6.x/7.x - can someone explain this?

error = EBUSY; goto fail; } So does anyone know whether it's safe to simply remove that test? Thanks, Arlie Stephens Engineer Dorr H. Clark Advisor Graduate School of Engineering Santa Clara University, Santa Clara, CA

gdb/libkvm problem - can someone explain this?

; goto invalid; } +#endif *pa = ofs; return (NBPDR - (va & PAGE4M_MASK)); } Does anyone see any problem or have any comments about this? Paul Lai Engineer Dorr H. Clark Advisor Graduate School of Engineering San

resource leak in fifo_vnops.c: 6.x/7.x/8.x

mtx_unlock(&fifo_mtx); + /* Exclusive VOP lock is held - safe to clean */ + fifo_cleanup(vp); return (ENXIO); } fip->fi_writers++; Test program follows. We welcome feedback on this proposed fix. Chitti Ni

MP & FreeBSD

this from being a mainstream capability? I can't promise any useful output from my work but I'd be happy to help with forward progress if possible. Thanks in advance for any useful information, -Dorr H. Clark Santa Clara University To Unsubscribe: send mail to [EMAIL PROTECTED] wit

need help: gdb -k 4.16/7

dentifier is reported only once trad-core.c:108: for each function it appears in.) *** Error code 1 Stop. < end gdb 4.16 build log excerpt > Anyone who has any clues as to how to overcome any of these problems, and properly access the old kernel core files using any of the 4.16, 4.17, or 4.18 bas

now OK, was - need help: gdb -k 4.16/7

code is doing the right thing the cores are completely debuggable. Thanks for the previous responses, it was helpful in straightening this bug out, -Dorr H. Clark Santa Clara University To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message