Summary:ASTERISK-09268: Asterisk crashes on Illegal instruction loading module codec_gsm.so
Reporter:George Baker (gbaker)Labels:
Date Opened:2007-04-16 13:05:48Date Closed:2011-06-07 14:00:49
Versions:Frequency of
Environment:Attachments:( 0) full
Description:Asterisk Crashes with an Illegal Instruction In gsm_sub (src/add.c) when initially loading the module codec_gsm.so. If I put this module in the modules.conf file as a noload, then asterisk will crash in codec_lpc10.so and if I don't load that module, then it crashes in codec_ilbc.so and if I don't load that module, the I finally get the CLI> prompt. However. once there, asterisk will crash on a sigsegv in process_sdp at chan_sip.c:4752 whan a call is placed on the sip device


I am running on a VIA ATX motherboard with 386MB RAM with a 20GB Hard drive.
I am running Debian 4.0 (Etch) which is the latest stable release.
gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
GNU Make 3.81 for i486-pc-linux-gnu
All other needed libraries were from the Debian Etch 4.0 release.

Let me know if anybody needs assitional information
Comments:By: Jason Parker (jparker) 2007-04-16 19:34:46

VIA?  At first glance, this sounds to me like an instruction set incompatibility.  Did you compile everything on that box, or did you use another box to compile?  There are some VIA chips (Nehemiah?) that don't fully support i686.

By: George Baker (gbaker) 2007-04-17 11:06:12

Everything was compiled on this box. The asterisk, the libpri and zaptel were all compiled here.

By: George Baker (gbaker) 2007-04-18 10:44:34

Some additional information. If I compile asterisk with the standard Optimization,  Asterisk will segv when it first tries to access argv and argc in the main function. If I turn optimization off, it then proceeds to act as initially indicated.

By: Tilghman Lesher (tilghman) 2007-04-18 23:44:48

Please upload the 'makeopts' file into the file upload area.

By: Joshua C. Colp (jcolp) 2007-05-17 10:30:53

It's been a month and the requested information still hasn't been added... if this is still an issue with something we are doing please reopen with the needed information.