free() pointer error in 4.53 12092009

[GoogleCodeExporter]

1. run indexer with -C option, answer "YES" then the database is cleared
and following error is received.

Deleting...Done
*** glibc detected *** ./indexer: free(): invalid pointer: 0x097e95b0 ***
======= Backtrace: =======
/lib/libc.so.6[0x38fb16]
/lib/libc.so.6(CFREE+0x90)[0x393030]
/usr/local/dpsearch/lib/libdpsearch-4.so(DpsDBFree+0x30)[0x916a90]
/usr/local/dpsearch/lib/libdpsearch-4.so(DpsDBListFree+0x35)[0x916bf5]
/usr/local/dpsearch/lib/libdpsearch-4.so(DpsEnvFree+0x46)[0x905896]
./indexer[0x804b530]
/lib/libc.so.6(__libc_start_main+0xdc)[0x33cdec]
./indexer[0x8049d91]

This error occurs on RHEL5 32-bit.

The same error occurs for many other commands.

Original issue reported on code.google.com by Imlbr...@gmail.com on 22 Sep 2009 at 8:21

[GoogleCodeExporter]

Which DBAddr do you use in your indexer.conf file ?

Original comment by dp.max...@gmail.com on 22 Sep 2009 at 8:48

[GoogleCodeExporter]

DBAddr
mysql://user:pass@localhost/dpsearch/?socket=/var/lib/mysql/mysql.sock@dbmode=mu
lti

Original comment by Imlbr...@gmail.com on 22 Sep 2009 at 9:22

[GoogleCodeExporter]

Perhaps you have mistype in your DBAddr, the second '@', before dbmode is 
incorrect,
try this one:
DBAddr
mysql://user:pass@localhost/dpsearch/?socket=/var/lib/mysql/mysql.sock&dbmode=mu
lti

Original comment by dp.max...@gmail.com on 23 Sep 2009 at 5:50

[GoogleCodeExporter]

The conf files are correct, the typo was only in my typing into the comment. So 
my
DBAddr is
mysql://user:pass@localhost/dpsearch/?socket=/var/lib/mysql/mysql.sock&dbmode=mu
lti
and the issue still occurs.

Original comment by Imlbr...@gmail.com on 23 Sep 2009 at 2:22

[GoogleCodeExporter]

Which switches have been used for configure to configure DataparkSearch ?

Original comment by dp.max...@gmail.com on 23 Sep 2009 at 5:51

[GoogleCodeExporter]

./configure --with-mysql --enable-rel=full --with-zlib --enable-googlegrp
--enable-reltrack

Original comment by Imlbr...@gmail.com on 23 Sep 2009 at 5:54

[GoogleCodeExporter]

Sorry, I can't reproduce this on my system. Could you, please, reconfigure with
--with-debug switch for configure and recreate backtrace ? With this switch 
specified
a more informative backtrace is produced.

Original comment by dp.max...@gmail.com on 23 Sep 2009 at 8:23

[GoogleCodeExporter]

Hi Maxime, I've attached the requested output.

Original comment by Imlbr...@gmail.com on 23 Sep 2009 at 9:23

Attachments:

• [dpsearch trace.txt](https://storage.googleapis.com/google-code-attachments/dataparksearch/issue-20/comment-8/dpsearch trace.txt)

[GoogleCodeExporter]

Maxime, this issue was due to an old version of the mysql_devel package on our
system. Thanks for your help.

Original comment by Imlbr...@gmail.com on 28 Oct 2009 at 5:43

[GoogleCodeExporter]

Thank you for reporting.

Original comment by dp.max...@gmail.com on 28 Oct 2009 at 6:09

• Changed state: Done