[asterisk-bugs] [JIRA] (ASTERISK-23717) Segfault when loading XML documentation
Walter Doekes (JIRA)
noreply at issues.asterisk.org
Thu May 22 07:23:44 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-23717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218378#comment-218378 ]
Walter Doekes commented on ASTERISK-23717:
------------------------------------------
Okay. So that valgrind output doesn't tell me much. Most likely because of all the BN_mod_inverse crap before.
You didn't rerun with --error-limit=no (or with exclude filters on libcrypto).
A couple of suggestions to try:
- rerun valgrind while attempting to get more info out of it
- try a more recent libxml2. the oldest version I run is 2.8.0, the newest is 2.9.1. yours are older
- if you can, remove the libxml2 package and compile it from source while making sure that optimization is disabled and debugging symbols are enabled
{{libxml2$ CFLAGS=-O0\ -g ./configure --with-debug}}
- try what happens if you remove BUILD_NATIVE from the asterisk build options (a 586 system is rather rare nowadays)
- a combination of the above
> Segfault when loading XML documentation
> ---------------------------------------
>
> Key: ASTERISK-23717
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-23717
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/General, Documentation
> Affects Versions: 11.9.0
> Environment: i586 - GLIBC_2.3.2
> Reporter: Hendrik Wedhorn
> Assignee: Walter Doekes
> Attachments: asterisk.conf, asterisk.inc, backtrace1190.txt, valgrind.txt
>
>
> When loading the xml documentation the asterisk always dies with an segmentation fault. Although this should not influence each other, this only happens when the /etc/asterisk/asterisk.conf has an include to an another file.
> - When the include in the asterisk.conf is removed the xml documentation is loaded perfectly fine. No segfault.
> - When the xml documentation is remove the include in the asterisk.conf works perfectly fine. No segfault.
> - The segfault always appears (100% reproducible.) when both is used.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list