Re: [Valgrind-users] Signal handling in 2.1.0

[Tom H. <th...@cy...>]

In message <107...@st...>
        Crispin Flowerday <val...@fl...> wrote:

> The program is a test case, where normally, and under previous versions
> of valgrind, it would exit after 1 second. However using 2.1.0 it just
> sits in the read() forever. This seems to be because the read() function
> call is getting restarted, which is not what normally happens.

[ snipped test case ]

> Shall I put this into bugzilla ?

Yes please. Looks like a problem with Jeremy's system call and signal
handling changes.

You can get the same result without using alarm by installing that
handler on SIGINT and then hitting Control-C to interrupt it - it
works normally but under valgrind the read gets restarted.

Tom

-- 
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/