Rainer Gerhards wrote: > Thanks for the excellent bug report. I have one idea based on a case I had in > the past. Can it be that Centos GCC version does not properly support atomic > instructions or is set to an to-old version?
That has crossed my mind as well and I've checked generated config.h which contains: /* Define if compiler provides atomic builtins */ /* #undef HAVE_ATOMIC_BUILTINS */ /* Define if compiler provides 64 bit atomic builtins */ /* #undef HAVE_ATOMIC_BUILTINS_64BIT */ So I thought the mutexes were being used and everything was fine with that. > I have one other case open, and > I think it was on centos. If atomics do no work right, nothing works well at > all in rsyslog. You mean that the #ifdef directives which fall back to mutex locking aren't good enough? > Note that the build system seems to be unable to correctly > detect this, as can be seen in this bug tracker here: > > http://bugzilla.adiscon.com/show_bug.cgi?id=202 Well, even if the configure check is not correct, it doesn't exibit false positive in my case. > Could you please rebuild it with -march=i586 added to the CFLAGS. If my idea > is right, it will probably run with that. I've tried and now config.h contains: /* Define if compiler provides atomic builtins */ #define HAVE_ATOMIC_BUILTINS 1 /* Define if compiler provides 64 bit atomic builtins */ #define HAVE_ATOMIC_BUILTINS_64BIT 1 However, it still crashes in the same way. -- .-. .-. Yes, I am an agent of Satan, but my duties are largely (_ \ / _) ceremonial. | | [email protected] _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
