[asterisk-bugs] [JIRA] (ASTERISK-24718) [patch]Add inital support of "sanitize" to configure
Kevin Harwell (JIRA)
noreply at issues.asterisk.org
Mon Dec 14 14:23:33 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-24718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Harwell closed ASTERISK-24718.
------------------------------------
Resolution: Fixed
> [patch]Add inital support of "sanitize" to configure
> ----------------------------------------------------
>
> Key: ASTERISK-24718
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24718
> Project: Asterisk
> Issue Type: Improvement
> Security Level: None
> Components: Core/BuildSystem
> Affects Versions: SVN, 11.15.0, 11.16.0, 13.3.2, 13.6.0
> Reporter: Badalian Vyacheslav
> Assignee: Badalian Vyacheslav
> Attachments: 1.diff, add_sanitize.diff, san-address.log, san-leak.log, san-thread.log.gz, san-undefined.log
>
>
> Tested on RedHat 6 with {{devtoolchain-3}} (gcc 4.9.1) installed
> after apply patch need run {{./bootstrap.sh}}
> {quote}
> Please update the issue description with what the patch is doing
> {quote}
> Path add support to use ASAN (https://code.google.com/p/address-sanitizer/wiki/AddressSanitizer) that was add to gcc 4.8+.
> You may use one of {{address}}, {{thread}} or {{memory}} sanitizer.
> To enable it you can simple do
> {{./configure --enable-sanitize=address}}
> {quote}
> and the reason the patch is being provided.
> {quote}
> Valgrind have poor perfomance... slow down 20x+ from native run.
> Address-sanitizer do only 2x slowdown, but break running after first error found.
> Becouse our production server have more 100 connected lines we can't test memory leaks.
> In valgrind run we can do only 5-7 connected lines :(
> Now we detect memory leaks using address-sanitizer.
> I'm provide patch to anyone else who want test with ASAN.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list