Date: Wed, 29 Nov 1995 09:16:27 +0100 (MET) From: grog@lemis.de (Greg Lehey) To: julian@ref.tfs.com (Julian Elischer) Subject: Re: Documentation.. Message-ID: <199511290817.JAA16566@allegro.lemis.de> In-Reply-To: <199511282246.OAA24442@ref.tfs.com> from "Julian Elischer" at Nov 28, 95 02:46:57 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer writes: > >> >>> Jordan K. Hubbard writes: >>> > >>> > > locking as the result of the change of struct flock. The binary I had >>> > > (elm) was compiled on BSD/386 1.1, and it didn't run on BSD/OS 2.0 >>> > > either. >>> > >>> > Now try compiling elm on BSD/OS 2.0 and running that under FreeBSD. That >>> > was what was referred to. >>> >>> Aha. How about that--it SIGSEGVs out of start. Is this known behaviour? >>> >>> Greg >> >> Uh. Greg, you really should read your mail more thoroughly. This is >> the issue you've been discussing WRT "BSDI compatibility" the whole >> time.. :-) >> >> Jordan >> > It'd be interesting to see what they were trying to achieve.... > anyone know WHY it SEGV's? > what does ktrace say? > gdb? gdb's the right tool. It's blowing up trying to set up a pointer to the environs, which BSDI keeps above the stack. FreeBSD doesn't have anything there, so it picks up a NULL pointer and bombs out. Any ideas about what the right way to handle this is? I have a number of pages of documentation (in ?roff or PostScript) which explain what's going on here, if anybody wants them. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511290817.JAA16566>