[tor-dev] Segfault trying to start tor in 0.2.4.16-rc with bufferevents

[Ian Goldberg]

On Thu, Aug 22, 2013 at 10:25:00AM -0400, Nick Mathewson wrote:
> On Thu, Aug 22, 2013 at 10:17 AM, Ian Goldberg <iang at cs.uwaterloo.ca> wrote:
> > I just tried to upgrade my tor exit node to 0.2.4.16-rc, and got this:
> 
> > I rebuilt without bufferevents, and it hasn't crashed yet.  (I also
> > don't see the "Something tried to close an or_connection_t" warnings.)
> 
> Seems likely.  This is a dup of bug
> https://trac.torproject.org/projects/tor/ticket/7734 .

Indeed.  (Though that bug doesn't report a segfault.)

> When you started Tor, did you get this warning?
> 
>   log_warn(LD_GENERAL, "Tor was compiled with the --enable-bufferevents "
>            "option. This is still experimental, and might cause strange "
>            "bugs. If you want a more stable Tor, be sure to build without "
>            "--enable-bufferevents.");

I didn't notice it, but things scrolled by quickly.

> (The bufferevent backend is not preferred in 0.2.3 or 0.2.4.  Maybe
> 0.2.5 is where somebody hammers all the bugs out of it.)

Ah, I had been under the mistaken impression it was good in 0.2.4.  No
worries.

Thanks,

   - Ian