[asterisk-bugs] [JIRA] (ASTERISK-25434) Since 13.4.0 Asterisk does not include DONT_OPTIMIZE or BETTER_BACKTRACES when enabled in menuselect

Rusty Newton (JIRA) noreply at issues.asterisk.org
Tue Sep 29 14:09:33 CDT 2015


Rusty Newton created ASTERISK-25434:
---------------------------------------

             Summary: Since 13.4.0 Asterisk does not include DONT_OPTIMIZE or BETTER_BACKTRACES when enabled in menuselect
                 Key: ASTERISK-25434
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25434
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Core/BuildSystem
    Affects Versions: 13.5.0, 13.4.0, SVN
         Environment: Ubuntu 12.04 , Linux newtonr-laptop 3.13.0-55-generic #94~precise1-Ubuntu SMP Thu Jun 18 09:53:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
            Reporter: Rusty Newton
            Severity: Blocker


This is a goofy one.

Description:

Before building Asterisk, enable DONT_OPTIMIZE or BETTER_BACKTRACES in menuselect. After building and installing check "core show settings" and see that those options are not reported.

I believe the flags are not actually set as I noticed the problem when I was reproducing a crash and saw optimizations in pjsip code despite having selected DONT_OPTIMIZE in menuselect.

Other options such as DEBUG_THREADS or DEBUG_FD_LEAKS seem to work fine.

Notes:


I *cannot* reproduce in 13.3.2, but I *can* reproduce in 13.4.0, 13.5.0 and a git pull of 13 branch from today.

I had [~kharwell] reproduce as well with a git pull from a few hours ago.

That all being said, I could swear these options worked fine (disabling and enabling between builds) in 13.5.0 for the past weeks... Very confusing.

I'm interested to see if others can reproduce.




--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list