[GH-ISSUE #1332] SIGABRT, SIGBUS, and SIGSEGV handler #714

New issue

Open

opened 2026-03-04 01:48:08 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:48:08 +03:00

Owner

Originally created by @gaul on GitHub (Jul 12, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1332

s3fs could log its stack trace during fatal signals to help debug issues. This would assist users who struggle with gdb as well as non-interactive situations like Travis CI.

Originally created by @gaul on GitHub (Jul 12, 2020). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1332 s3fs could log its stack trace during fatal signals to help debug issues. This would assist users who struggle with `gdb` as well as non-interactive situations like Travis CI.

kerem added the

enhancement

label

2026-03-04 01:48:08 +03:00

kerem commented

2026-03-04 01:48:09 +03:00

Author

Owner

@ggtakec commented on GitHub (Jul 12, 2020):

This could help our debugging if we are testing s3fs with travis CI.
I will consider to be able to output stack information when receiving a signal.
In the case of gdb, I think it may be unnecessary because gdb handles it by self.

@ggtakec commented on GitHub (Jul 12, 2020): This could help our debugging if we are testing s3fs with travis CI. I will consider to be able to output stack information when receiving a signal. In the case of gdb, I think it may be unnecessary because gdb handles it by self.

kerem commented

2026-03-04 01:48:09 +03:00

Author

Owner

@gaul commented on GitHub (Nov 29, 2020):

Here is one approach:

https://stackoverflow.com/questions/77005/how-to-automatically-generate-a-stacktrace-when-my-program-crashes

@gaul commented on GitHub (Nov 29, 2020): Here is one approach: https://stackoverflow.com/questions/77005/how-to-automatically-generate-a-stacktrace-when-my-program-crashes

kerem referenced this issue

2026-03-04 02:01:20 +03:00

[PR #714] [MERGED] reduce lock contention on file open #1617