[subexp-daq] Report of a possible bug with "log_level=spam"

[Hans Toshihide Törnqvist]

Dear Günter,

That is definitely a bug in nurdlib, thanks for finding it!

It looks like some log call which opens a new scope with "{" does not have a proper corresponding closing curly bracket log. Is there more information in the drasi log file by any chance? I will look through the relevant code meanwhile, but if you find more lines before the error appears it would help a lot.

(This also reminds me to evaluate nurdlib log scopes agai, since it requires very careful ha sling of actual C scope...) 

Best regards,
Hans



"Weber, Guenter Dr." <g.weber at hi-jena.gsi.de> skrev: (15 februari 2024 20:31:00 CET)
>Dear friends,
>
>
>while playing around with the DAQ, I got the following problem right at the start of the DAQ:
>
>
>5: util/log.c:319: ..........Log indent overflow: "..........Gsi Vulom readout_dt {".
>5: util/log.c:319: ..........Calling abort()...
>
>
>In my main.cfg I had just a single VULOM active.
>
>
>log_level=spam # info, verbose, debug, spam
>
>CRATE("MCAL") {
>    GSI_VULOM(0x03000000) {
>        timestamp = true # needed to get timestamps in the data output
>    #   ecl=0..15
>    }
>#   BARRIER
>#   DUMMY(0x01000000) {
>#   }
>}
>
>
>If the log_level is reduced to debug, the error does not occur and the system is running with problems.
>
>
>I am using the most recent version of NURDLIB.
>
>
>Attached please find the full output of the RIO when the DAQ is started.
>
>
>
>
>
>Best greetings
>
>Günter
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chalmers.se/pipermail/subexp-daq/attachments/20240215/f9649341/attachment.html>