You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use this package to diagnose a nasty hang that shows up seemingly at random (or at least, is hard to reliably reproduce). Something that would be useful for that is to have a log of every command that Emacs executes, dumped to a file in chronological order (i.e., as the commands happen). That seems to be well within the capabilities of this package, and seems to be the point of explain-pause-log-to-socket. However, I haven't been able to get that command to work: Every time I try to run it, I get the error:
Explain-pause-mode stopped logging to socket. It got too full.
I've tried this with both the default and custom explain-pause-logging-default-location, with the same results.
Am I interpreting this feature correctly? And, if so, could you provide an example configuration / a brief explanation of how to set it up?
The text was updated successfully, but these errors were encountered:
ashiklom
changed the title
Continuously log all functions to file?
Continuously log all function calls to file?
Oct 9, 2020
I'm trying to use this package to diagnose a nasty hang that shows up seemingly at random (or at least, is hard to reliably reproduce). Something that would be useful for that is to have a log of every command that Emacs executes, dumped to a file in chronological order (i.e., as the commands happen). That seems to be well within the capabilities of this package, and seems to be the point of
explain-pause-log-to-socket
. However, I haven't been able to get that command to work: Every time I try to run it, I get the error:I've tried this with both the default and custom
explain-pause-logging-default-location
, with the same results.Am I interpreting this feature correctly? And, if so, could you provide an example configuration / a brief explanation of how to set it up?
The text was updated successfully, but these errors were encountered: