<snip>
Thanks Steven. If I had not been so desperately hoping that there were no hardware problems on this machine, I might have suspected this myself. I'll try to track down memory issues next. Thanks again to you and RobYou apparently still have quite a bit more to learn. If you read the first line quoted, you will see that it is the compiling that is a problem. At no time during compile is the application you are compiling actually executed. Only gcc and it's helpers should be executed. Gcc is notorious for finding bad memory as it sprawls out over large sections and is sensitive to bits flipping around. If Asterisk was segfaulting, then there may be a question as to whether asterisk behaved differently under load(timing issues) or if it was still bad memory.
Stephen R. Besch
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
