After kernel debug with “fw ctl debug” you received a huge amount of information. It was saved in a very large file that is difficult to open and analyze with standard text editors. Suggest a solution to solve this issue.
A.
Use “fw ctl debug” because of 1024KB buffer size
B.
Divide debug information into smaller files. Use “fw ctl debug -f -o “filename” -m 25 -s “1024”
C.
Reduce debug buffer to 1024KB and run debug for several times
D.
Use Check Point InfoView utility to analyze debug output
fw ctl debug defines what you want to debug and which flags for debugging are used, and it stores debugging information to a buffer not a file. fw ctl kdebug collects the debug, and you can redirect its output to a file.
B could be a solution if the command was fw ctl kdebug, instead of fw ctl debug.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
thehill
4 months, 3 weeks agonmrouter
6 months ago