[GitHub] [nuttx] GooTal opened a new issue, #8959: Enabling sinfo printing and disabling CONFIG_SYSLOG_TIMESTAMP_REALTIME caused a recursive calling bug?

[via GitHub]

GooTal opened a new issue, #8959:
URL: https://github.com/apache/nuttx/issues/8959

   I enabled sinfo printing:
   
![图片](https://user-images.githubusercontent.com/40800103/229732968-65422dbe-1ae7-4bd5-a722-ff7e2e28a15a.png)
   
   I found that sinfo called nx_vsyslog, then called clock_gettime
   ```
     if (OSINIT_HW_READY())
       {
   #if defined(CONFIG_SYSLOG_TIMESTAMP_REALTIME)
         /* Use CLOCK_REALTIME if so configured */
   
         clock_gettime(CLOCK_REALTIME, &ts);
   
   #else
         /* Prefer monotonic when enabled, as it can be synchronized to
          * RTC with clock_resynchronize.
          */
   
         clock_gettime(CLOCK_MONOTONIC, &ts);
   #endif
   ```
   But clock_gettime called sinfo again, which makes a recursive bug?
   
   Here`s the backtrace from gdb:
   
   
![图片](https://user-images.githubusercontent.com/40800103/229732230-965566fe-7e83-40b5-8e43-9cca54ec4fe3.png)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org