the sched can be null in cases where the connection has not been registered into the scheduler OR a plugin has created a socket which is not part of the main queue, but.. for that specific function there is no issues
On Sat, Mar 24, 2012 at 4:09 PM, Felipe Astroza <[email protected]> wrote: > In mk_plugin.c you can find the function mk_plugin_event_add. It is called > in worker thread context and it has sched structure always. If you take a > glance in mk_scheduler, you'll find the next lines in > mk_sched_launch_worker_loop(): > ... > thinfo = &sched_list[wid] > ... > pthread_setspecific(worker_sched_node, (void *) thinfo); > > > 2012/3/24 Lauri Kasanen <[email protected]> >> >> On Sat, 24 Mar 2012 08:27:59 -0600 >> Eduardo Silva <[email protected]> wrote: >> >> > Hi, >> > >> > not applicable. mk_bug() must be used just to avoid bad parameters by >> > the developer. Also exists some conditions where the sched node can be >> > NULL and not necessary its a bug. >> >> Ok. But if sched can be NULL, monkey would segfault in >> mk_epoll_add(sched->epoll_fd, socket, mode, behavior); >> ^^^^^^ here. >> >> Perhaps that should be moved inside the if then? >> >> -- >> - Lauri >> >> _______________________________________________ >> Monkey mailing list >> [email protected] >> http://lists.monkey-project.com/listinfo/monkey > > -- Eduardo Silva http://edsiper.linuxchile.cl http://www.monkey-project.com _______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
