Skip to content

ARROW-14733: [R] Add section to how to get output when things hang to debugger docs #11723

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
thisisnic wants to merge 1 commit into from
Closed

ARROW-14733: [R] Add section to how to get output when things hang to debugger docs #11723

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion r/vignettes/developers/debugging.Rmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,14 +75,31 @@ Here is debugger output from the segfault shown in the previous example. You
can see here that the exact line which triggers the segfault is included in the
output.

```
```shell
> S3FileSystem$create()

Thread 1 "R" received signal SIGSEGV, Segmentation fault.
0x00007ffff0128369 in std::__atomic_base<long>::operator++ (this=0x178) at /usr/include/c++/9/bits/atomic_base.h:318
318 operator++() noexcept
```

#### Getting debugger output if your session hangs

The instructions above can provide valuable additional context when a segfault
occurs. However, there are occasionally circumstances in which a bug could
cause your session to hang indefinitely without segfaulting. In this case, it
may be diagnostically useful to interrupt the debugger and generate backtraces
from all running threads.

To do this, firstly, press Ctrl/Cmd and C to interrupt the debugger, and then run:

```shell
thread apply all bt
```

This will generate a large amount of output, but this information is useful when
identifying the cause of the issue.

## Resources

The following resources provide detailed guides to debugging R code:
Expand Down