Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-2884

LOG() macro fails if message is a simple std::string

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Won't Fix
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: log
    • Labels:
      None
    • Story Points:
      1.5
    • Sprint:
      DB_S15_06, DB_S15_07, DB_S15_08, DB_W16_09
    • Team:
      Data Access and Database

      Description

      lsst:log LOG() macro crash with fatal error if message is a simple string.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          tjenness Tim Jenness added a comment -

          Shall I look at this since I'm meant to be looking at the log package anyhow?

          Show
          tjenness Tim Jenness added a comment - Shall I look at this since I'm meant to be looking at the log package anyhow?
          Hide
          Permalink
          jbecla Jacek Becla added a comment -

          That'd be welcome

          Show
          jbecla Jacek Becla added a comment - That'd be welcome
          Hide
          Permalink
          tjenness Tim Jenness added a comment -

          Fabrice Jammes can you tell me how to trigger this? Naively using a std::string as an argument to LOG causes a compiler error for me as it can't find a valid constructor for a std::string.

          Show
          tjenness Tim Jenness added a comment - Fabrice Jammes can you tell me how to trigger this? Naively using a std::string as an argument to LOG causes a compiler error for me as it can't find a valid constructor for a std::string .
          Hide
          Permalink
          jammes Fabrice Jammes added a comment -

          Hi Tim Jenness,

          Sorry but I can't reproduce thos problem no more. As far as I can remember I met this kind of problem:

          LOGF(LOG_GET("testLogger"), LOG_LVL_INFO, "This was crashing the program if no parameters where provided");
          		 
          // but
          		 
          LOGF_DEBUG("This was working");

          Both of them seems to works now so I propose to set this ticket state to "won't fix"?

          Cheers,

          Show
          jammes Fabrice Jammes added a comment - Hi Tim Jenness , Sorry but I can't reproduce thos problem no more. As far as I can remember I met this kind of problem: LOGF(LOG_GET( "testLogger" ), LOG_LVL_INFO, "This was crashing the program if no parameters where provided" ); // but LOGF_DEBUG( "This was working" ); Both of them seems to works now so I propose to set this ticket state to "won't fix"? Cheers,
          Hide
          Permalink
          tjenness Tim Jenness added a comment -

          Closed as we can no longer reproduce. Re-open if we do demonstrate it again.

          Show
          tjenness Tim Jenness added a comment - Closed as we can no longer reproduce. Re-open if we do demonstrate it again.

            People

            Assignee:
            tjenness Tim Jenness
            Reporter:
            jammes Fabrice Jammes
            Watchers:
            Fabrice Jammes, Jacek Becla, Kian-Tat Lim, Tim Jenness
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: