[ 
https://issues.apache.org/jira/browse/ARROW-8217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067094#comment-17067094
 ] 

Neal Richardson commented on ARROW-8217:
----------------------------------------

I managed to run with gdb (included in Rtools) like this: 

{code}
C:\Program Files\R\R-3.6.0\bin\i386>\Rtools\mingw_32\bin\gdb R.exe
{code}

Unfortunately, there's no backtrace on exit:

{code}
Start test: IPC/Arrow format data
  test-dataset.R#172:1 [success]
  test-dataset.R#173:1 [success]
[Inferior 1 (process 4920) exited with code 030000000005]
(gdb) bt
No stack.
(gdb)
{code}

Retrying with {{break exit}}, there's nothing useful, presumably because R 
needs to be rebuilt with debug symbols:

{code}
Start test: IPC/Arrow format data
  test-dataset.R#172:1 [success]
  test-dataset.R#173:1 [success]
Breakpoint 1, 0x767866f5 in msvcrt!exit () from C:\Windows\System32\msvcrt.dll
(gdb) bt
#0  0x767866f5 in msvcrt!exit () from C:\Windows\System32\msvcrt.dll
#1  0x00405787 in ?? ()
#2  0x004013e2 in ?? ()
#3  0x74ea6359 in KERNEL32!BaseThreadInitThunk () from 
C:\Windows\System32\kernel32.dll
#4  0x77247b74 in ntdll!RtlGetAppContainerNamedObjectPath () from 
C:\Windows\SYSTEM32\ntdll.dll
#5  0x77247b44 in ntdll!RtlGetAppContainerNamedObjectPath () from 
C:\Windows\SYSTEM32\ntdll.dll
#6  0x00000000 in ?? ()
(gdb)
{code}

On the one hand, no backtrace could mean that it's not a segfault, just some 
other hard exit. On the other, googling the exit code comes up with lots of 
hits suggesting that it is a segfault.

If someone wants to tell me other ideas of places to set breakpoints or 
whatever to try to see what's failing, I can try. I can also try making a DEBUG 
build of Arrow C++ (this is a release build). I'd rather not have to build R 
from source to get more debug symbols.


> [R][C++] Fix crashing data in test-dataset.R on 32-bit Windows from ARROW-7979
> ------------------------------------------------------------------------------
>
>                 Key: ARROW-8217
>                 URL: https://issues.apache.org/jira/browse/ARROW-8217
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++, R
>            Reporter: Wes McKinney
>            Priority: Major
>             Fix For: 0.17.0
>
>
> If we can obtain a gdb backtrace from the failed test in 
> https://github.com/apache/arrow/pull/6638 then we can sort out what's wrong. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to