Re: malloc crash

[dpuu]

You don't show any code, so I'll answer using generalities.

As a general rule, you should do as little as possible in a signal handler. Typical actions would be to set a flag (which will be detected in the mainline code), or to increment a semaphore (to wake up a thread -- to continue processing). --Dave

[Nygeve]

So there is neither any magic "i want safe signals" option no newest signals safe version of perl?
I didn't post any code because i think this is a general problem: simple daemon that updates mysql db once per 10 sec using alarm signal.

[hossman]

I didn't post any code because i think this is a general problem: simple daemon that updates mysql db once per 10 sec using alarm signal.

That's like saying "I didn't post any code, because it's just a little CGI that does some stuff and prints HTML" ... the devil is in the details.

As a general rule: If you have a question about why some code doesn't do what you expect. Post the code (or the smallest sample program that demonstrates the problem).

In situations where your question concerns an err msg you are getting, the "general rule" becomes the golden rule: If you are getting an eror, from code you think should work, post a sample program that generates the error, and the exact text of the error, along with your question.

[Nygeve]

"As a general rule: If you have a question about why some code doesn't do what you expect. Post the code (or the smallest sample program that demonstrates the problem)."
Ok, agree. But i must say that this question is not about one piece of code that doesn't want to work. This question is about common problem in perl(sorry) - signals and malloc(you can of course call it more smartly, kinda low level interaction of perl and cpp methods or what ever). I saw questions from people about this(google,you know e.t.c.), but (i)didn't find any clear answer. So i didn't want to bother anyone with the another snippet with the same problem. Just wanted a quick answer(help).