[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [Libevent-users] 14k vprintf evbuffer on solaris
- To: libevent-users@xxxxxxxxxxxxx
- Subject: Re: [Libevent-users] 14k vprintf evbuffer on solaris
- From: Nick Mathewson <nickm@xxxxxxxxxxxxx>
- Date: Mon, 4 Oct 2010 13:43:21 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: libevent-users-outgoing@xxxxxxxx
- Delivered-to: libevent-users@xxxxxxxx
- Delivery-date: Mon, 04 Oct 2010 13:43:27 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=ZbDFC+TWO1/r6a7hFZ/Keh6T2WuKLpXB9HvcNSdXClc=; b=vjn8FTVwuZrSk9m8IbuKCG++4lQ0ISd0Jh1P3KGGxewAejiAbGkDtoMwpTWzZCl4Q+ dc1dbm12fB4+yWFwXZC5YLMItgESWvnbevfQ51rzmMM6X+JYXWCbTPZkn+KLyuMXkNUF xYhdRT0iHlUWYqjH2YXboNljppfnWH+NCuZzw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=uuxmPNdko4fQ0kWDQX4ASPNydaop5rCgDSpgs3MS2AIX8HeoIo6ZY6g1uTUz1Mb4VU BUSCzLYRzck9TdPz7kOJOpQcCdVwAKFPkCX42AYCTuUgehNFwqn4PrlzlNwzGPp1VKQD jTQ5SMoPzwLzWjVJEPyIA+dcJE53dP27ngrD0=
- In-reply-to: <4CA3B0EC.4050603@xxxxxxxxx>
- References: <4CA3B0EC.4050603@xxxxxxxxx>
- Reply-to: libevent-users@xxxxxxxxxxxxx
- Sender: owner-libevent-users@xxxxxxxxxxxxx
On Wed, Sep 29, 2010 at 5:34 PM, Michael Herf <herf@xxxxxxxxx> wrote:
[...]
> Has anyone else seen a failure case like this? (I'm going to dig in and see
> what I can find.)
I haven't seen this before, no.
One way to try to debug this would be to check would be to figure out
where, along the chain between you adding the data and the data
getting sent out via writev(), the data is getting lost. Possible
places are:
1) The data isn't getting added to the evbuffer.
2) The data is getting added, but the bufferevent isn't delivering it.
3) Data is getting added and bufferevent *should* be delivering it,
but for some reason the evhttp code is screwing everything up.
Another possible way to try to chase this down would be to use git
bisect to try to figure out what change broke this on opensolaris.
If these don't work, have an opensolaris vm I could try to use to
help, but I would need an example of a _minimal_ test program that
worked okay on (say) Linux, but failed on OpenSolaris.
hth,
--
Nick
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users in the body.