Date: Fri, 16 Jan 1998 12:43:38 +1030 From: Greg Lehey <grog@lemis.com> To: Alex <garbanzo@hooked.net> Cc: FreeBSD Hackers <hackers@FreeBSD.ORG> Subject: Re: Why no sys/setjmp.h? Message-ID: <19980116124338.44216@lemis.com> In-Reply-To: <Pine.BSF.3.96.980115144707.253A-100000@zippy.dyn.ml.org>; from Alex on Thu, Jan 15, 1998 at 02:49:43PM -0800 References: <19980115201816.30399@lemis.com> <Pine.BSF.3.96.980115144707.253A-100000@zippy.dyn.ml.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 15, 1998 at 02:49:43PM -0800, Alex wrote: > On Thu, 15 Jan 1998, Greg Lehey wrote: > >> On Thu, Jan 15, 1998 at 12:16:49AM -0800, Alex wrote: >>> On Thu, 15 Jan 1998, Greg Lehey wrote: >>> >>>> I'm just writing kernel code which uses setjmp and longjmp, and I >>>> discover that there are no header files with declarations of these >>>> functions. How come? Are they deprecated in the kernel? Should I be >>>> using something else instead? >>> >>> man 3 setjmp >> >> I'm writing *kernel* code. > > I don't think it maeks a big difference. setjmp(3) is a user library routine. It's not the same thing as kernel setjmp. > zippy:/usr/src/sys#grep setjmp */*.c > ddb/db_command.c:#include <setjmp.h> > ddb/db_command.c: (void) setjmp(db_jmpbuf); > ddb/db_trap.c:#include <setjmp.h> > ddb/db_trap.c: if (setjmp(db_jmpbuf) == 0) > zippy:/usr/src/sys#find . -name "setjmp.h" > ./i386/include/setjmp.h > ./alpha/include/setjmp.h > > You can try the same thing in the sys/i386 dir if you really wanted > examples from i386/i386 ;-) Thanks. That was the answer: I wasn't searching /sys/i386/include for my header files. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980116124338.44216>