[asterisk-bugs] [JIRA] (ASTERISK-23221) Asterisk Crash on 32bit Linux with MALLOC_DEBUG enabled

[Wolfgang Liegel (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214685#comment-214685 ] 

Wolfgang Liegel edited comment on ASTERISK-23221 at 1/31/14 12:53 AM:
----------------------------------------------------------------------

Attached my asterisk.conf.
But I can also reproduce the crash even without any asterisk.conf on my system at all.

I'm building with
gcc (GCC) 4.3.2 20081105 (Red Hat 4.3.2-7)
                
      was (Author: wliegel):
    Attached my asterisk.conf.
But I can also reproduce the crash even without any asterisk.conf on my system at all.
                  
> Asterisk Crash on 32bit Linux with MALLOC_DEBUG enabled
> -------------------------------------------------------
>
>                 Key: ASTERISK-23221
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23221
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Configuration, Core/General, Core/PBX
>    Affects Versions: 1.8.20.0, 1.8.25.0
>         Environment: Fedora Core 10
> Kernel 2.6.27.41-170.2.117.fc10.i686 #1 SMP i686 i686 i386 GNU/Linux
> asterisk 1.8.25.0
>            Reporter: Wolfgang Liegel
>            Assignee: Wolfgang Liegel
>         Attachments: asterisk.conf, core.txt
>
>
> On a 32bit Fedora 10 I see an Segmentation Fault during startup process.
> This crash is reproducible by enabling MALLOC_DEBUG.
> This issue was first introduced with Version 1.8.20.0 and is still reproducible in version 1.8.25.0.
> Maybe this is due to changes from https://reviewboard.asterisk.org/r/2182/
> According to the core dump the crash occours right after reading asterisk.conf.
> The crash occurs before any output is written to log or stdout.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira