I have been extremely careful to be as clean as possible. The stack
trace catching is implemented with a PreDebuggingAction without
overriding any of the existing code. It was one of my first design
goals, especially because the purpose of the tool is to be completely
pluggable and unpluggable without influencing the system.
Also, we tested it for three months in daily development activities,
so it is reasonably stable.
We are analyzing the stack traces we collected so far to see if what
useful information a developer can obtain from that. I would love to
see ShoreLine Reporter used to help the development of the Pharo
ecosystem and I would be glad to help if you think that such a tool
could be useful if integrated into Pharo.
Sounds promising :)
