Menu

#2 free() error

v1.0 (example)
open
nobody
None
5
2015-05-20
2015-05-13
Rick Huff
No

The following charge.conf creates a free error (double free or corruption (fasttop)):

<charge>
<server name="default" host="hostname.utexas.edu" port="636" protocol="ldaps"/>
<list name="bindop">
<items>
<item value="username here"/>
<item value="password here"/>
</items>
</list>
<seq nb="10" it="10">
<op type="bind" nb="1" name="bindop"/>
<op type="unbind" nb="1"/>
</seq>
</charge>

Related

Bugs: #2

Discussion

  • Raphaël Ouazana

    I have already seen this with old versions of libldap_r. Which versions do you use?

     
    • Rick Huff

      Rick Huff - 2015-05-19

      /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2.8.3

      This is under Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-51-generic x86_64) Rick Huffrhuff2@yahoo.com

        From: Raphaël Ouazana <rouazana@users.sf.net>
      

      To: [loadtesting:bugs] 2@bugs.loadtesting.p.re.sf.net
      Sent: Tuesday, May 19, 2015 5:22 AM
      Subject: [loadtesting:bugs] #2 free() error

      I have already seen this with old versions of libldap_r. Which versions do you use?

      [bugs:#2] free() error Status: open
      Group: v1.0 (example)
      Created: Wed May 13, 2015 04:51 PM UTC by Rick Huff
      Last Updated: Wed May 13, 2015 04:51 PM UTC
      Owner: nobodyThe following charge.conf creates a free error (double free or corruption (fasttop)):<charge>
      <server name="default" host="hostname.utexas.edu" port="636" protocol="ldaps"/>
      <list name="bindop">
      <items>
      <item value="username here"/>
      <item value="password here"/>
      </items>
      </list>
      <seq nb="10" it="10">
      <op type="bind" nb="1" name="bindop"/>
      <op type="unbind" nb="1"/>
      </seq>
      </charge>Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/loadtesting/bugs/2/To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       

      Related

      Bugs: #2

  • Raphaël Ouazana

    Sometimes I can reproduce this bug, using libldap-2.4-2 (based on OpenLDAP 2.4.31)?.
    But if I use a custom OpenLDAP build, I can't see this issue anymore.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.