Per Jessen wrote:
This is a runtime check? I'll try it. I get the situation about once a day.
The -D_FORTIFY_SOURCE=2 didn't change anything.
In the meantime I've changed my vsyslog() call to a call to vsnprintf+syslog - which didn't change anything. So maybe the right question is - is syslog() threadsafe?
Well, I'm still seeing the following about once a day: a chunk of heap which I've malloc'ed is overwritten by a syslog line (from another thread): <23>Apr 27 03:08:46 distripg[20987]: response[2/1219288]: The <23> is very indicative of syslog(). I'm tempted to guard my syslog() call with an explicit mutex and see if that changes anything. /Per Jessen, Zürich --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-programming+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-programming+help@opensuse.org