How do I debug cutechess-cli engine input/output?

[Toadofsky]

I'm trying to enable self-learning in Sunsetter (in which I compiled w/learning enabled and set learning=1).

What confuses me is that the -debug command-line option doesn't seem to result in anything displayed or logged?

Code: Select all

  -debug                Display all engine input and output

Code: Select all

cutechess-cli -debug -variant crazyhouse -openings file=crazyhouse.pgn format=pgn -engine cmd=Sunsetter/sunsetter -engine cmd=Sunsetter/sunsetter -each proto=xboard tc=240/60+1 -pgnout sunsetter.pgn

(crazyhouse.pgn contains openings 1. d4 and 1. e4,)

[elcabesa]

-debug option print to screen all the comunication between cutechess and the engines. It will not add any new information to pgn file.

[mroh]

For writing an cutechess-cli webfrontend I had the same problem on linux:

To get anything from -debug I had to:

vi ~/.config/QtProject/qtlogging.ini and set "*.debug" to true:
*.debug=true

[Ferdy]

I'm trying to enable self-learning in Sunsetter (in which I compiled w/learning enabled and set learning=1).

What confuses me is that the -debug command-line option doesn't seem to result in anything displayed or logged?

Code: Select all

  -debug                Display all engine input and output

Code: Select all

cutechess-cli -debug -variant crazyhouse -openings file=crazyhouse.pgn format=pgn -engine cmd=Sunsetter/sunsetter -engine cmd=Sunsetter/sunsetter -each proto=xboard tc=240/60+1 -pgnout sunsetter.pgn

(crazyhouse.pgn contains openings 1. d4 and 1. e4,)

In windows I saved the debug to a file with >

cutechess-cli -debug -variant crazyhouse -openings file=crazyhouse.pgn format=pgn -engine cmd=Sunsetter/sunsetter -engine cmd=Sunsetter/sunsetter -each proto=xboard tc=240/60+1 -pgnout sunsetter.pgn > debug.txt