On Sat, 18 Dec 2010 14:25:54 -0500 Mike Blumenkrantz <m...@zentific.com> said:

> On Sat, 18 Dec 2010 20:11:27 +0100
> Cedric BAIL <cedric.b...@free.fr> wrote:
> 
> > On Sat, Dec 18, 2010 at 7:15 PM, Mike Blumenkrantz <m...@zentific.com>
> > wrote:
> > > On Sat, 18 Dec 2010 18:49:53 +0100
> > > Andreas Volz <li...@brachttal.net> wrote:
> > >> Am Fri, 17 Dec 2010 21:13:59 -0500 schrieb Mike Blumenkrantz:
> > >>
> > >> > On Sat, 18 Dec 2010 10:44:00 +0900
> > >> > Carsten Haitzler (The Rasterman) <ras...@rasterman.com> wrote:
> > >> >
> > >> > > main_fd_handler_add() Failed to add
> > >> > > > poll on fd 18 (errno = 17)! ERR<14518>:ecore ecore.c:227
> > >> > > > _ecore_magic_fail() *** ECORE ERROR: Ecore Magic Check Failed!!!
> > >> > > > *** IN FUNCTION: ecore_main_fd_handler_active_set()
> > >> > > > ERR<14518>:ecore ecore.c:229 _ecore_magic_fail()   Input handle
> > >> > > > pointer is NULL! ERR<14518>:ecore ecore.c:240 _ecore_magic_fail()
> > >> > > > *** NAUGHTY PROGRAMMER!!! *** SPANK SPANK SPANK!!!
> > >> > > > *** Now go fix your code. Tut tut tut!
> > >> > > > ERR<14518>:ecore ecore_main.c:758 ecore_main_fd_handler_add()
> > >> > > > Failed to add poll on fd 18 (errno = 17)! ERR<14518>:ecore
> > >> > > > ecore.c:227 _ecore_magic_fail() *** ECORE ERROR: Ecore Magic
> > >> > > > Check Failed!!!
> > >> > Try disabling epoll support in ecore and see if you still get this
> > >> > same same error.
> > >>
> > >> I compiled with --disable-epoll and all works again. I tied to update
> > >> to an older revision and use --enable-epoll, but compilation failed.
> > >>
> > >> I don't know what's the functional meaning of this option, but I'm
> > >> happy with disabling it. :-)
> > >>
> > >> regards
> > >>       Andreas
> > >>
> > >> ------------------------------------------------------------------------------
> > >> Lotusphere 2011
> > >> Register now for Lotusphere 2011 and learn how
> > >> to connect the dots, take your collaborative environment
> > >> to the next level, and enter the era of Social Business.
> > >> http://p.sf.net/sfu/lotusphere-d2d
> > >> _______________________________________________
> > >> enlightenment-devel mailing list
> > >> enlightenment-devel@lists.sourceforge.net
> > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
> > > The current epoll code will error when you try to add the same fd twice
> > > (bad behavior to begin with), so your only choice is to not use epoll
> > > currently. This may change in the future depending on the whims of the
> > > other Mike.
> > 
> > Does that mean, I can't have two different callback watching the same fd ?
> With epoll I think not.

that actually wouldnt work right anyway - you fd HANDLERS ... handle an fd -
that is handle the reads and writes to/from it when its needed. 2 fd handlers
for the same fd will fail badly ad 1 fd handler will get in first and do a read
for example - then "take the data" - the second will not be able to read that
data anymore. it's gone. already read. so... it never made any sense to hand 2
fd handlers for 1 fd. it's pretty much an invalid thing to do. so i don't think
this is a epoll vs select thing here. it just should never have happened or
worked right anyway. epoll just errors out differently. the select code doesnt
- you just get implicit errors instead as above.

so the question is... is it really adding the same fd twice - and if so.. why
was it doing that? that "userspace" code needs fixing if it did.


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ras...@rasterman.com


------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to