I've finally been able to answer my own question. Execute the following
and no more PharoDebug.log and no more stack dump to stdout/stderr (I'm
not exactly sure which debugger is being used, so I set both for good luck):
DebugSession logDebuggerStackToFile: false.
GTGenericStackDebugger logDebuggerStackToFile: false.
While writing this message I found that there does appear to be a
setting that controls this (I used the double click trick on "Log file
name" and followed it to the above messages), but I haven't actually
tested it:):
On 7/31/19 4:58 PM, Dale Henrichs wrote:
It appears that the PharoDebug.log can be dropped into the directory
from which a Pharo image is launched ... I would have expected it to
be dropped into the local directory, but that does not appear to be
the case ...
I've looked in the Settings Browser and there does not appear to be a
way to influence the location of the PharoDebug.log.
I am currently using the `st` command line handler if that is important.
I've googled for PharoDebug.log to no avail.
Any help will be appreciated,
Dale
