Yep... the build process actually pulled a completely fresh copy of
libevent when compiling the transmission-daemon. I'll do some more
debugging over the weekend. Maybe I can find out, where the rogue event
is coming from.
Frank
Niels Provos provos-at-citi.umich.edu |libevent| wrote:
Here is a silly question for you. Did you you do a make clean after
svn up? There have also been some changes to the autoconf files in
trunk that might require running autogen again.
Niels.
On Fri, Feb 22, 2008 at 1:54 AM, Frank Schaeckermann
<[EMAIL PROTECTED]> wrote:
I have installed transmission-daemon (a Bittorrent client) svn revision
5051 on my Maxtor Shared Storage II (ARM little endian) with Linux
2.6.12. Very soon after starting the daemon it segfaults.
I have re-compiled and re-installed transmission-daemon with debug
information and ran it in gdb. The segfault happens in epoll.c line 217
(libevent svn revision 651) in epoll_dispatch. Apparently an event comes
in that does not have its data pointer set properly. I fixed the problem
by adding a check for a valid data pointer before doing anything with it
and now transmission does not segfault anymore.
But the event that is to be dispatched now does not do anything anymore.
Which means I have cured the symptoms but not the cause. Somebody needs
to figure out, why and from where invalid events get to epoll_dispatch.
Or maybe it is okay if that happens, but then epoll.c needs to be
patched accordingly.
If there is anything I can help with, please let me know!
Regards, Frank
P.S. I have already posted this in the transmissionbt forum but was
asked by the developers to report it upstream to libevent as well.
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
