On 8/7/19 11:32 AM, Torsten Bergmann wrote:
Dale wrote:
I used the double click trick on "Log file name" and followed it to the above
messages
for the records:
Beside double click you can also right click on a setting and select "Browse"
to find
where it is implemented. You can then also "S
Dale wrote:
>I used the double click trick on "Log file name" and followed it to the above
>messages
for the records:
Beside double click you can also right click on a setting and select "Browse"
to find
where it is implemented. You can then also "Save" the current settings.
The settings frame
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
I think Smalltalk logFileName: is what you want
On Wed, Jul 31, 2019, 20:58 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
