Mailinglist Archive: opensuse-programming (6 mails)
| < Previous | Next > |
Re: [opensuse-programming] is vsyslog() reentrant / thread-safe?
- From: Per Jessen <per@xxxxxxxxxxxx>
- Date: Tue, 22 Apr 2008 08:14:01 +0200
- Message-id: <fujvna$1eg$1@xxxxxxxxxxxxxxxx>
Philipp Thomas wrote:
This is a runtime check? I'll try it. I get the situation about once a
day.
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?
/Per Jessen, Zürich
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-programming+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-programming+help@xxxxxxxxxxxx
On Mon, 21 Apr 2008 18:35:34 +0200, Per Jessen wrote:
I've several core dumps that all point to vsyslog() being the culprit.
I've got a chunk of heap-storage being overwritten by a formatted
logline:
Have you tried compiling the app with -D_FORTIFY_SOURCE=2? This will
add runtime stack and buffer overflow checking to your code (this is
what nearly all code in openSUSE is compiled with and helps quite a
lot) and may help in finding the place where the app blows up.
This is a runtime check? I'll try it. I get the situation about once a
day.
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?
/Per Jessen, Zürich
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-programming+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-programming+help@xxxxxxxxxxxx
| < Previous | Next > |