From: Bob Alexander <balexander@...>
Date: 2001-07-13T04:37:13+09:00
Subject: [ruby-talk:17744] Re: Strange warning

> |Here is the code fragment again, with the line marked where the warning
> |occurs. I'm hoping someone has a clue as to why this is happening. The
> |surrounding code is included just to provide context. Note that the
> |warning does not occur every time this code executes -- only
> |occasionally, and I haven't figured out a pattern yet. The code appears
> |to execute correctly despite the warning, though.
>
> Hmm, I don't think I can reproduce the bug.  I think I need whole of
> your program to reproduce.  Is it possible?
>

It would be hard, since it depends on a lot of environment being set up.
I'm trying to create a smaller, more independent program that causes the
error, but have been unsuccessful so far.

I did learn something, though. It has something to do with signals. The
program that gets the warning is catching SIGUSR1 signals sent by other
processes. I prevented the other processes from signaling it, and the
warnings stopped!

I'll post again if I can create a test program you could execute in your
environment.

Bob