[asterisk-bugs] [JIRA] (ASTERISK-29576) Scope Tracing: format string is not a string literal

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29576:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> Scope Tracing: format string is not a string literal
> ----------------------------------------------------
>
>                 Key: ASTERISK-29576
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29576
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Logging
>    Affects Versions: 16.20.0, 18.6.0
>         Environment: Clang 12.0.0-3 of Ubuntu 21.04
>            Reporter: Alexander Traud
>
> This issue was introduced with [GERRIT-14463|https://gerrit.asterisk.org/14463]. Why ever, the compiler Clang but not GCC is not complaining about this.
> *Steps to Reproduce* (see {{contrib/scripts/install_prereq}}):
> {code}
> sudo apt install make clang libblocksruntime-dev pkg-config
> sudo apt install libedit-dev libjansson-dev libsqlite3-dev uuid-dev libxml2-dev
> CC=clang CXX=clang++ ./configure --enable-dev-mode=noisy
> make
> {code}
> *Result*:
> {code}
> logger.c:2449:50: error: format string is not a string literal [-Werror,-Wformat-nonliteral]
>         ast_log_full(__LOG_TRACE, -1, NULL, 0, NULL, 0, ast_str_buffer(fmt), ap);
>                                                         ^~~~~~~~~~~~~~~~~~~
> {code}Unsure what to do about this. The comments on Gerrit indicate that this code snippet is still under investigation. I could disable this particular error for the file {{./main/logger.c}} in Developer Mode, in general or just for Clang. Any suggestions? Or we ignore this issue because nobody (?) is using Clang with the Developer Mode of Asterisk. Not sure.



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