search for: linprocfs_misc

...details The following list contains the revision numbers of each file that was corrected in FreeBSD. Branch Revision Path - ------------------------------------------------------------------------- RELENG_4 src/sys/i386/linux/linprocfs/linprocfs_misc.c 1.3.2.9 src/sys/kern/kern_subr.c 1.31.2.3 src/sys/miscfs/procfs/procfs_dbregs.c 1.4.2.4 src/sys/miscfs/procfs/procfs_fpregs.c 1.11.2.4 src/sys/miscfs/procfs/procfs_regs.c...

...details The following list contains the revision numbers of each file that was corrected in FreeBSD. Branch Revision Path - ------------------------------------------------------------------------- RELENG_4 src/sys/i386/linux/linprocfs/linprocfs_misc.c 1.3.2.9 src/sys/kern/kern_subr.c 1.31.2.3 src/sys/miscfs/procfs/procfs_dbregs.c 1.4.2.4 src/sys/miscfs/procfs/procfs_fpregs.c 1.11.2.4 src/sys/miscfs/procfs/procfs_regs.c...

...unctioning properly, but this module failed with an "exec format error". Further investigation revealed that nextpid was undefined. So i checked the source, and discovered that in kern/kern_fork.c, nextpid was defined statically. It was defined nowhere else, but in i386/linux/linprocfs/linprocfs_misc.c, it was declared "extern". Since the system needed a new pair of shoes anyway, i promptly upgraded it to 4.8-STABLE. To my surprise, i found that nothing had changed. The nextpid variable was still defined as a "static int" in kern_fork.c, and it was still requested external...