the more proper thing would be to configure with --with-malloc=checking or --with-malloc=slow
Then Kannel would detect this issue itself.


On 23.08.2006, at 17:54, Guillaume Cottenceau wrote:

Stipe Tolj <st 'at' tolj.org> writes:

Randel Rock wrote:

I am using Centos 4.2 i386 on an intel p3 machine.
 I get this error:
 Check: checks/check_http.sh... checking SSL connections, too...***
glibc
detected *** free(): invalid pointer: 0x08513688 ***
 FAILURE!
Check: checks/check_httpsmsc_kannel.sh... OK.
Check: checks/check_ppg.sh...wap failed with control file
test/iptestppg.txt
bb failed with control file test/iptestppg.txt
wap failed with control file test/smstestppg.txt
bb failed with control file test/smstestppg.txt
 FAILURE!

so this is a glibc panic situation.... what should we say here? -> out

No, this means that the glibc memory allocation functions
detected an incorrect free call in the running code - most
probably *not* in the glibc code, though not strictly impossible.

One might want to run the offending program through valgrind to
easily spot the problem.

-- 
Guillaume Cottenceau
Create your personal SMS or WAP Service - visit http://mobilefriends.ch/




Andreas Fink
Fink Consulting GmbH
---------------------------------------------------------------
Tel: +41-61-6666332 Fax: +41-61-6666331  Mobile: +41-79-2457333
Address: Clarastrasse 3, 4058 Basel, Switzerland
---------------------------------------------------------------
ICQ: 8239353
MSN: [EMAIL PROTECTED] AIM: smsrelay Skype: andreasfink
Yahoo: finkconsulting SMS: +41792457333




Reply via email to