Fwd: [plt-scheme] v300 on OpenBSD

I ran into similar problems trying to compile on OpenBSD.  I believe that I got a core dump, but I moved onto other things before I was able to look into exactly what was going on.  OpenBSD plays several tricks with memory, and how it maps pages, along with the stack-manipulation stuff that was mentioned previously.  The good news is that it can be turned off, and it can be useful for finding overflow and other memory related bugs.  To turn off the stack protection code (propolice) use the -fno-stack-protector, you may also want to look at the malloc man page as it has more information on some of the tricks they play (and how to get around them).  I'll report on any progress I make if I get around to playing with it some more.

Evan

> >>development snapshot of libffi you're using. Still, I've heard there
> >>are issues with libffi and the stack-manipulation stuff that OpenBSD
> >>does, so caveat programmor.

On Mon, Dec 26, 2005 at 10:03:39PM +0000, Patrick Collison wrote:
> Got this from Eli, he thinks it's probably a buffering issue:
> 
> Begin forwarded message:
> 
> >From: Eli Barzilay <eli at barzilay.org>
> >Date: 26 December 2005 21:23:34 GMT+00:00
> >To: Patrick Collison <patrick at collison.ie>
> >Subject: Re: [plt-scheme] v300 on OpenBSD
> >
> >
> >On Dec 26, Patrick Collison wrote:
> >
> >>On 26 Dec 2005, at 19:58, Eli Barzilay wrote:
> >>
> >>
> >>>On Dec 26, Patrick Collison wrote:
> >>>
> >>>
> >>>>Hi,
> >>>>
> >>>>I'm trying to compile v300 of mzscheme on OpenBSD-CURRENT. I ran
> >>>>configure with --prefix=/usr/local and --disable-foreign, because
> >>>>I don't know of any good libffi port for OpenBSD. configure and
> >>>>make ran without any issue.
> >>>>
> >>>
> >>>I don't know of any problems libffi has on freebsd.
> >>>
> >>
> >>OpenBSD isn't a supported platform according to the site.
> >>
> >
> >Ah, as usual, I always confuse the *BSDs.
> >
> >
> >
> >>I added
> >>
> >>i*86-*-openbsd*) TARGET=X86; TARGETDIR=x86;;
> >>
> >>to the libffi configure script and things seem to go okay with
> >>it. It might be worth adding this permanently to whatever
> >>development snapshot of libffi you're using. Still, I've heard there
> >>are issues with libffi and the stack-manipulation stuff that OpenBSD
> >>does, so caveat programmor.
> >>
> >
> >I'll leave it as is, until libffi changes.
> >
> >
> >
> >>The libffi change has also changed my problem (slightly):
> >>
> >>setup-plt:   in /usr/local/plt/collects/mzlib/private/
> >>setup-plt: Compiling .zos used by MzLib
> >>setup-plt:   in /usr/local/plt/collects/mzlib/
> >>setup-plt: No more .zos to compile for MzScheme
> >>setup-plt: Compiling .zos used by Net
> >>setup-plt:   in /usr/local/plt/collects/net/
> >>setup-plt:   in /usr/local/plt/collects/srfi/13/
> >>setup-plt:   in /usr/local/plt/collects/srfi/14/
> >>setup-plt:   in /usr/local/plt/collects/net/private/
> >>setup-plt: Compiling .zos used by Parser-tools private-yacc
> >>setup-plt:   in /usr/local/plt/collects/parser-tools/private-yacc/
> >>setup-plt:   in /usr/local/plt/collects/parser-tools/private-lex/
> >>setup-plt: Compiling .zos used by Parser-tools private-lex
> >>setup-plt:   in /usr/local/plt/collects/parser-tools/private-lex/
> >>setup-plt: Compiling .zos used by Parser-tools
> >>setup-plt:   in /usr/local/plt/collects/parser-tools/
> >>setup-plt:   in /usr/local/plt/collects/syntax/
> >>
> >>It seems to be getting a little bit further, now hanging on
> >>compiling syntax. Is there any good way of diagnosing what might be
> >>going?  Would I be right in assuming that the change in problem
> >>points towards a problem with the compiler itself rather than the
> >>collects?
> >>
> >
> >It's probably a buffering problem somewhere.  Matthew?
> >
> >--  
> >          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli  
> >Barzilay:
> >                  http://www.barzilay.org/                 Maze is  
> >Life!
> >
> >
> 
> _________________________________________________
>  For list-related administrative tasks:
>  http://list.cs.brown.edu/mailman/listinfo/plt-scheme