Wes Hardaker wrote: > I think without looking further into the issue, I'd say -1. If it's > known to cause segfaults on x86_64 (as the comment applies) then it > would be better to change the ifdef to a point where we know it's safe > now, or go back to the original perl version that the problem appeared > with and see if the problem has gone away. > > (what I'm worried about is not that on a recent system with a recent > 5.10 perl everything works just fine; it's on some older system with > some unknown (but still distributed) perl it'll break)
Do you really think I'm just blindly backing out my own workaround (hack) re-introducing my own bug without looking at my own comments? Bug 1494882 has the details of the original crash problem (causing "make test" to fail) that I've been reporting for RHEL3/x86_64 and RHEL4/x86_64 (but probably not limited to them). I still have access to the very same machines with their original configuration (same Perl version and such). Current 5.2.x SVN (with the patch in question applied) passes "make test" on these machines. BTW, you've been heavily arguing against the #ifdef hack in the first place back then, but don't let it stop you from voting for its persistence now that the alternative isn't a fancy segfault, but just normal operation. ;-) +Thomas ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
