On Tue, Mar 27, 2012 at 4:35 PM, William Lima wrote:
> On Fri, Mar 23, 2012 at 12:54 AM, Nick Mathewson
> wrote:
>>
>> On Thu, Mar 22, 2012 at 9:18 PM, Mark Ellzey wrote:
>> > On Thu, Mar 22, 2012 at 07:11:01PM -0300, William Lima wrote:
>> >> Hi!
>> >>
>> >> I'm using bufferevent in my proxy pr
On Tue, Mar 27, 2012 at 5:35 PM, William Lima wrote:
> On Fri, Mar 23, 2012 at 12:54 AM, Nick Mathewson wrote:
>
>> On Thu, Mar 22, 2012 at 9:18 PM, Mark Ellzey wrote:
>> > On Thu, Mar 22, 2012 at 07:11:01PM -0300, William Lima wrote:
>> >> Hi!
>> >>
>> >> I'm using bufferevent in my proxy proje
On Thu, Mar 22, 2012 at 9:18 PM, Mark Ellzey wrote:
> On Thu, Mar 22, 2012 at 07:11:01PM -0300, William Lima wrote:
>> Hi!
>>
>> I'm using bufferevent in my proxy project and I have a bug. The entire
>> program is single-thread, but apparently the error callback can be called
>> while something is
On Thu, Mar 22, 2012 at 08:18:21PM -0500, Mark Ellzey wrote:
> On Thu, Mar 22, 2012 at 07:11:01PM -0300, William Lima wrote:
> > Hi!
> >
> > I'm using bufferevent in my proxy project and I have a bug. The entire
> > program is single-thread, but apparently the error callback can be called
> > whil
On Thu, Mar 22, 2012 at 07:11:01PM -0300, William Lima wrote:
> Hi!
>
> I'm using bufferevent in my proxy project and I have a bug. The entire
> program is single-thread, but apparently the error callback can be called
> while something is still running (ie. a parser) into server/client read
> cal
Hi!
I'm using bufferevent in my proxy project and I have a bug. The entire
program is single-thread, but apparently the error callback can be called
while something is still running (ie. a parser) into server/client read
callbacks, causing a segmentation fault, since the error callback destroy
the
