On Tue, Apr 23, 2013 at 6:36 PM, ольга крыжановская <[email protected]> wrote: > Michal, I can reproduce the bug on Suse 12.3 with a 64bit > ast-ksh.2013-04-22 in PATH to run iffe. What crashes is this: > > + /bin/cp dbm.req > /home/test001/work/ast_ksh_20130422/build_32bit_plain/arch/linux.i386-64/lib/lib/dbm > + mamake -C lib/libast -k install > probing C language processor > /home/test001/work/ast_ksh_20130422/build_32bit_plain/arch/linux.i386-64/bin/cc > for mam information > + iffe -v -X ast -X std -c 'cc -D_BLD_DLL -fPIC -D_BLD_ast -O2 ' > run > /home/test001/work/ast_ksh_20130422/build_32bit_plain/src/lib/libast/features/standards > iffe: cc -D_BLD_DLL -fPIC -D_BLD_ast -O2 -c ./suse35823.c > iffe: line 38: 35827: Memory fault > iffe: cc: core dump or fatal interruption -- results inconclusive > mamake [lib/libast]: *** exit code 11 making FEATURE/standards > > package make was called through > CC='gcc -m32' /bin/ksh ./bin/package make 2>&1 | tee -a buildlog.log
I took a look at Olga's crash... the stack trace is different from Michals and only happens for ast-open builds but not if the same sources are build with ast-ksh... then I rebuild the tree to test something else and... erm... the bug is... gone (which means I don't have a stack trace either... still digging...). My guess is that there is a sporadic issue somewhere in the build system for ast-open (but not ast-ksh) which causes these "glitches" (Michal's issue may be a seperate one...) ... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [email protected] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
