[asterisk-bugs] [JIRA] (ASTERISK-20612) Segmentation fault related to pthread stack size with LOW MEMORY compiler flag selected

[Stephen Hinton (JIRA)]

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

Stephen Hinton commented on ASTERISK-20612:
-------------------------------------------

Hi Matt, I am having problems generating a backtrace. You see the segmentation fault only occurs when launching asterisk via amportal in FreePBX whereas when launching asterisk standalone you get the same error but no segmentation fault. Please advise as to how to proceed, could not find a core file 
                
> Segmentation fault related to pthread stack size with LOW MEMORY compiler flag selected
> ---------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20612
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20612
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 10.10.0
>         Environment: Debian Wheezy with all updates (DebWrt), Asus RT-N16 router (480Mhz, 128mb ram, O/S on usb)
>            Reporter: Stephen Hinton
>            Assignee: Stephen Hinton
>
> Compiled asterisk with the low memory flag selected. Upon trying to start asterisk manually (asterisk -cvvvd) the following output is printed:
> "utils.c:1056 ast_pthread_create_stack: pthread_attr_setstacksize: Invalid argument"
> When starting with amportal start:
> "(debwrt-mipsel)root at debwrt:~# amportal start
> Please wait...
> SETTING FILE PERMISSIONS
> chown: cannot access `/dev/tty9': No such file or directory
> Permissions OK
> STARTING ASTERISK
> pthread_attr_setstacksize: Invalid argument
> Segmentation fault
> Asterisk ended with exit status 139
> Asterisk exited on signal 11.
> Automatically restarting Asterisk."

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira