[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[Libevent-users] Unitialized Memory Read when pushing >64 events at once
- To: libevent-users@xxxxxxxxxxxxx
- Subject: [Libevent-users] Unitialized Memory Read when pushing >64 events at once
- From: Scott Dorr <j.scott.dorr@xxxxxxxxx>
- Date: Sun, 29 May 2011 17:27:36 -0700
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: libevent-users-outgoing@xxxxxxxx
- Delivered-to: libevent-users@xxxxxxxx
- Delivery-date: Sun, 29 May 2011 20:27:45 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=ks7Atm9If9LnQ5Tl/gT81biOXDKWw8syBBIkXF96MYw=; b=uXsmDiDOHWfAKdMzuPUaqBM6BG5fIUdOQv4WmnD1IugW6xFAvAHLZcrYB6oYHw8yKF nvh4f+8EsSAl0QySYBzzDzL/RBna4A+l1dCWtEyFa8Oseec6aNjFqfmZ5Ygs5lwSPCXf 4n89x/UeKJiTOBClZQ3hNB51Ta5XfpgiDlgUk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=GpDR0o34saRzJxyIirdTWbxCcXBt89lZW/J88akmkAzgvT6QqyT2sQaD7iC82waJzJ wvmXegiYEw/4ttXDX/O6uYbJfsJDqVLBy4iqC8KoUJEkMYPUf/NDgSLS2VSoeLe5wLk6 CRuV72tysaHuhB/qeY1eHusUDgWi1+HCPeoUA=
- Reply-to: libevent-users@xxxxxxxxxxxxx
- Sender: owner-libevent-users@xxxxxxxxxxxxx
Purify complains about Unitialized Memory Reads when I try to push more than 64 events onto the queue at the same time. This is in a 64bit application running on RHEL linux. I'm currently using libevent-2.0.10-stable.
epoll_dispatch triggers a set of of 4 UMRs for each event past the 64th that I push onto the event base. The first three are 1 byte reads on the stack (which it says is 20 bytes below the frame pointer in the epoll_dispatch function), and the fourth is a 4 byte read which is 388 bytes into a malloc'd block of 768 bytes. That malloc'd block was a realloc() that was called by epoll_dispatch->event_mm_realloc_
I don't have libevent instrumented, otherwise I'd provide more detail. Is this a known issue?