Re: [Boost-build] bjam define=anything produces a core dump

Subject: Re: [Boost-build] bjam define=anything produces a core dump
From: Vladimir Prus (ghost_at_[hidden])
Date: 2010-11-29 06:38:36

On Monday, November 29, 2010 13:40:25 Avi Bahra wrote:
> > On Linux, and HPUX, I can successfully use:
> >      bjam define=fred
> > 
> > On AIX:
> >    This produces a core dump
> > 
> > # bjam define=PORTABLE_BINARY_ARCHIVE
> > ...patience...
> > ...patience...
> > Segmentation fault (core dumped)
> > # bjam -v
> > Boost.Jam  Version 3.1.17. OS=AIX.
> > 
> >    Copyright 1993-2002 Christopher Seiwald and Perforce Software, Inc.
> >    Copyright 2001 David Turner.
> >    Copyright 2001-2004 David Abrahams.
> >    Copyright 2002-2008 Rene Rivera.
> >    Copyright 2003-2008 Vladimir Prus.
> > 
> > trying different variations like:
> >    bjam define=fred -n
> >    bjam -j2 -q define=bill=1
> > 
> > have no effect, all cause a crash, it appears that bjam cant cope with
> > defines on AIX?
> 
> Vladimir Prus wrote:
> >>I would imagine a miscomplication. Please have bjam built with debug
> >>symbols (./build.sh --debug) and produce a backtrace of the crash.
> 
> I have compiled bjam from boost 1.45 release in debug ( bjam 3.1.19)
> here is what total view shows when bjam crashes:
> 
> list_new,                                                 
> FP=ffffffffffd32c0 var_expand,          

IIUC, you also reported some problems whereby the compiler warns that you
have maximum memory size of a process set too low?

This might be a manifestation of the same problem. Undo all limits and
try agian.

- Volodya

-- 
Vladimir Prus
http://vladimir_prus.blogspot.com
Boost.Build: http://boost.org/boost-build2