#1 2025-02-11 17:03:40

zen010101
Member
Registered: 2024-06-15
Posts: 106

Issues about Remote Logging

When TSynLog.Family.PerThreadLog := ptIdentifiedInOneFile will prevent messages from being sent to the remote LogView. I did not find any explanation in any documentation or code comments, is this a feature or bug?

Offline

#2 2025-02-12 14:45:43

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,934
Website

Re: Issues about Remote Logging

I suspect it is a bug, because I currently don't use this feature.

Try to investigate a little bit more, and if you can't find the root cause and propose a pull request, please create an issue in GitHub.

Offline

#3 2025-02-13 16:41:02

zen010101
Member
Registered: 2024-06-15
Posts: 106

Re: Issues about Remote Logging

I did some debugging, the reason I suspect might be : TSynLogFile.ProcessOneLine. It determines whether the log file contains ThreadID based on whether the first line of formal message contains '!'. The first message sent when starting the Server in Logview.exe is: '%00 info Remote Logging Server started on port % with root name "%"'.

However, I do not know how to modify TSynLogFile to dynamically adapt to log content.


BTW: This line has a bug:

      if LineBeg[fLineLevelOffset] = 'Z' then

should be

      if LineBeg[fLineLevelOffset-2] = 'Z' then

Last edited by zen010101 (2025-02-13 16:41:15)

Offline

Board footer

Powered by FluxBB