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
Currently, ProFTPD has some support for logging stacktraces in e.g. the face of a SIGSEGV signal -- but only if the --enable-devel=stacktrace compile-time option is used. Those stacktrace logging can be very useful when diagnosing errors, and especially when users report errors. That being the case, why not have stacktrace support enabled by default, rather than disabled by default? There would then be a --disable-stacktrace compile-time option offered, of course.
Note that in order for stacktrace logging to work, the installed binaries must not be stripped. Thus when working on this feature, make sure to adjust the Makefiles' install targets accordingly.
The text was updated successfully, but these errors were encountered:
I'd like to get this enhancement into 1.3.6, in order to support #254 . Specifically, I'd like to include stack traces in the logged errors, when necessary. See also this pull request.
Currently, ProFTPD has some support for logging stacktraces in e.g. the face of a
SIGSEGV
signal -- but only if the--enable-devel=stacktrace
compile-time option is used. Those stacktrace logging can be very useful when diagnosing errors, and especially when users report errors. That being the case, why not have stacktrace support enabled by default, rather than disabled by default? There would then be a--disable-stacktrace
compile-time option offered, of course.Note that in order for stacktrace logging to work, the installed binaries must not be stripped. Thus when working on this feature, make sure to adjust the Makefiles'
install
targets accordingly.The text was updated successfully, but these errors were encountered: