#5 app_cbmysql - __ast_malloc

[Anonymous]

It appears that work has already been done in trying to correct the issue with Trixbox 2.8/Asterisk 1.6 as originally reported by jhainsworth.
However, the last deployed patch of this file is now indicating an undefined symbol error. As this was the 2nd attempt at creating the patch my hope is that the issue has not been considered solved. Perhaps you can revisit the issue to provide a working update for this module.

[Jul 9 13:00:22] WARNING[2822] loader.c: Error loading module 'app_cbmysql.so': /usr/lib/asterisk/modules/app_cbmysql.so: undefined symbol: __ast_malloc
[Jul 9 13:00:22] WARNING[2822] loader.c: Module 'app_cbmysql.so' could not be loaded.

[Dan_Austin]

The version of app_cbmysql under WMM does not use __ast_malloc, so it is likely that the version in TB has been customized.

Please attach a copy of the original file in TB and any patches and I can try to review them.

[Anonymous]

Thanks Dan! Below are the cases associated with each patch, description of issue along with the attached files for your reference.

2894784 - First issue reported with app_cbmysql.so (original file included with Trixbox 2.8)
Issue reported as resolved along with release of app_cbmysql.so-patch1

[Nov 9 10:58:27] WARNING[3347]: loader.c:636 inspect_module: Module 'app_cbmysql.so' was not compiled with the same compile-time options as this version of Asterisk.
[Nov 9 10:58:27] WARNING[3347]: loader.c:637 inspect_module: Module 'app_cbmysql.so' will not be initialized as it may cause instability.
[Nov 9 10:58:27] WARNING[3347]: loader.c:675 load_resource: Module 'app_cbmysql' could not be loaded.

2896876 - An issue was reported from attempts to use the patch1 file in this case. Case was then reported resolved along with a new release of the file (patch2).

Current: Patch2 is now reporting the __ast_malloc error.

[Anonymous]

Original file included with TB 2.8

[Anonymous]

First patch released - case 2894784

[Anonymous]

Second patch released - case 2896876

[MirkoBrankovic]

Was this ever resolved?

[Dan_Austin]

I am not sure. The original and current code do not use __ast_malloc, so the problem is likely with changed that the TB team made. I do not have their source, so I can only guess to what they have or have not done.