Dear Marc,
As that function is a template, it is only instantiated when used. I think
I've sent you sample programs regarding the issue, but I'll attach another
one:
#include ev++.h
int main()
{
ev::io x;
x.feed_event(ev::READ);
return 0;
}
Regards,
Kojedzinszky
If I have started a io_watcher with EV_READ event, but later I want to set
EV_WRITE event in callback function of EV_READ, should I have to call
ev_io_stop first, then ev_io_set and ev_io_start again?
If all messages have been send, should I call ev_io_stop again, clear EV_WRITE
event and
On Mon, Jun 11, 2012 at 4:39 AM, 钱晓明 mailtoanta...@163.com wrote:
If I have started a io_watcher with EV_READ event, but later I want to set
EV_WRITE event in callback function of EV_READ, should I have to call
ev_io_stop first, then ev_io_set and ev_io_start again?
If all messages have been
Hi,
Below is a patch that fixes a theoretical array overrun. I say theoretical
because I don't think there is a signal number high enough to trigger this. But
any ways... the issue is EV_NSIG starts off being 65. Then the array is declared
as signals [EV_NSIG - 1]; Which means 0-63 would be
On Mon, Jun 11, 2012 at 08:43:03AM -0400, Steve Grubb sgr...@redhat.com wrote:
if signum is 65, it won't return. This gets decremented to 64 and then used as
an index for a memory write. This is 1 over the top since 63 is the largest
valid index. I doubt this causes any problems, but a patch
