[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2933 [Tor Client]: Error from libevent: evdns.c:1360: Assertion req != port->pending_replies failed in server_port_flush
#2933: Error from libevent: evdns.c:1360: Assertion req != port->pending_replies
failed in server_port_flush
------------------------+---------------------------------------------------
Reporter: mr-4 | Owner:
Type: defect | Status: needs_review
Priority: normal | Milestone:
Component: Tor Client | Version: Tor: 0.2.2.24-alpha
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by mr-4):
Replying to [comment:9 nickm]:
> Yup. Apply it to libevent-2.0.10, and make sure that the version of tor
you're using is really linked against the updated libevent.
>
> If the patch *doesn't* work, and you know how to use gdb, it would be
good to get a stack trace here, and to see the values of "port",
"port->pending_replies", and *port->pending_replies".
>
> Otherwise, if the patch doesn't work, and you *don't* know how to use
gdb, I'll try to come up with another patch to dump a bunch of debugging
info or something.
OK, I now inadvertently changed the description of this bug :((( Sorry
about that, is there any way I could restore the previous description?
Originally, I meant to post this instead:
Damn!
I just realised that I have to build this from source! Nick, if you are
reading this I would (possibly) need some assistance!
The machine on which all this is going to run is very old i686 (Pentium2)
box, which has a read-only (locked up) kernel code and libraries (it runs
as part of my dmz). I normally build the entire image for this machine
(Fedora kickstart file) on my dev machine (x86_64 Core2).
That means I would need to 1) be able to cross-compile libevent2 (never
attempted that before); and 2) build Fedora rpm so that my kickstart could
use it.
From what I remember Rawhide for FC15 has libevent2 (2.0.10), which means
that I would be able to grab the source rpm. Even though I have
successfully altered the .spec file for quite a few packages to enable
them to cross-compile successfully (one reason I am banging on about
libevent-devel to be changed to enable cross-compilation!) it is not a
precise science.
Are there any peculiarities in libevent2 I should be aware of before I
attempt to do cross-compilation of libevent2 (I will, of course, report
back here if there are problems)?
As for your request above Nick, I haven't used gdb for about 8 years, so
it is safe to say that I wouldn't be able to use it (grumble).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2933#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs