Additional data when segfaulting #2216
Comments
nvartolomei
added a commit
to nvartolomei/rp-seastar
that referenced
this issue
May 4, 2024
Backtraces are printed in at least 2 cases: 1) during segfaults, 2) during reactor stalls. Extra context is always helpful in identifying the exact circumstances during which the above happen. E.g. in a server application where user requests are processed in one (or more) scheduling group(s), background processes are split between different scheduling groups as well, knowing the scheduling group narrows the search space. Ref scylladb#2216
nvartolomei
added a commit
to nvartolomei/rp-seastar
that referenced
this issue
May 4, 2024
Backtraces are printed in at least 2 cases: 1) during segfaults, 2) during reactor stalls. Extra context is always helpful in identifying the exact circumstances during which the above happen. E.g. in a server application where user requests are processed in one (or more) scheduling group(s), background processes are split between different scheduling groups as well, knowing the scheduling group narrows the search space. Prior to this commit: ``` Segmentation fault on shard 0. Backtrace: ... ``` With this commit: ``` Segmentation fault on shard 0, in scheduling group main. Backtrace: ... ``` Ref scylladb#2216
nvartolomei
added a commit
to nvartolomei/rp-seastar
that referenced
this issue
May 8, 2024
Backtraces are printed in at least 2 cases: 1) during segfaults, 2) during reactor stalls. Extra context is always helpful in identifying the exact circumstances during which the above happen. E.g. in a server application where user requests are processed in one (or more) scheduling group(s), background processes are split between different scheduling groups as well, knowing the scheduling group narrows the search space. Prior to this commit: ``` Segmentation fault on shard 0. Backtrace: ... ``` With this commit: ``` Segmentation fault on shard 0, in scheduling group main. Backtrace: ... ``` Ref scylladb#2216
nvartolomei
added a commit
to nvartolomei/rp-seastar
that referenced
this issue
May 8, 2024
Backtraces are printed in at least 2 cases: 1) during segfaults, 2) during reactor stalls. Extra context is always helpful in identifying the exact circumstances during which the above happen. E.g. in a server application where user requests are processed in one (or more) scheduling group(s), background processes are split between different scheduling groups as well, knowing the scheduling group narrows the search space. Prior to this commit: ``` Segmentation fault on shard 0. Backtrace: ... ``` With this commit: ``` Segmentation fault on shard 0, in scheduling group main. Backtrace: ... ``` Ref scylladb#2216
xemul
pushed a commit
that referenced
this issue
May 14, 2024
Backtraces are printed in at least 2 cases: 1) during segfaults, 2) during reactor stalls. Extra context is always helpful in identifying the exact circumstances during which the above happen. E.g. in a server application where user requests are processed in one (or more) scheduling group(s), background processes are split between different scheduling groups as well, knowing the scheduling group narrows the search space. Prior to this commit: ``` Segmentation fault on shard 0. Backtrace: ... ``` With this commit: ``` Segmentation fault on shard 0, in scheduling group main. Backtrace: ... ``` Ref #2216 Closes #2221
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently a segfault is reported as:
I believe we could add additional data about the context in which the segfault happens to aid debugging. I believe we should have access to the current scheduling group name, maybe tasktrace too. Anything else?
The text was updated successfully, but these errors were encountered: