Comment #2 on issue 99 by [email protected]: Memcached 1.4.2 server
segmentation fault
http://code.google.com/p/memcached/issues/detail?id=99
I'm going to punt on this from 1.4.3-rc1 - if we can reproduce and find the
bug
before 1.4.3-final we'll include it, however.
I'm staring at this really hard and while the proposed patch should fix it
(and is
how we do things in some other libevent-based projects), the claim of where
it
crashed is sounding impossible via logic errors.
event_del() relies on c->event.ev_base being *correct*. So in this case
somewhere
between event_del() and event_base_set(), the '*base' pointer is getting
removed or
corrupted.
It's also possible the segfault is really in event_del() but isn't
manifesting until
later? Maybe? I'd like to work with the user with full stack traces and a
core dump..
So again, I feel like the patch will fix the problem, but also that it
would hide
something that's potentially way more serious. I'd like to put some extra
scruitiny
on the bug just in case. Apologies for it taking so long to take a look,
and thanks
for filing a great bug report :)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
