I'm sure ST has ways of capturing stack traces in log files, but, casually, nobody talks about it.
With smalltalk the user could send you the image in its current state which would provide a lot more context than just a stack trace and a log. I definitely would prefer to pickup a running environment at the point of failure than a log when solving a bug. I cannot imagine how one would keep up with security on a setup like that though.
Back in 1990, 3½-inch 1.44 MB micro floppy disks were snail-mailed to me — a Smalltalk/V 286 image file, sources file and change log; for a system I'd developed a year or two before.
The "image in its current state" had been saved with an open "Walkback Window" showing an exception.
I opened the debugger, identified and fixed the problem (iirc without needing to reshape any user data with become:) and resumed the exception; saved the image and change log to the micro floppy disks, and snail-mailed them back.
Apparently the users picked-up their work where they'd left-off, when they sent it to me.
With smalltalk the user could send you the image in its current state which would provide a lot more context than just a stack trace and a log. I definitely would prefer to pickup a running environment at the point of failure than a log when solving a bug. I cannot imagine how one would keep up with security on a setup like that though.