lidavidm commented on issue #15054:
URL: https://github.com/apache/arrow/issues/15054#issuecomment-1385510661

   I think it's an AWS SDK issue again!
   
   I enabled catchsegv here: 
https://github.com/ursacomputing/crossbow/actions/runs/3939847223/jobs/6740188523
   
   The crashing instruction is at 0x7fed49842bb7:
   
   ```
   Backtrace:
   
/usr/local/lib/python3.9/site-packages/pyarrow/libarrow.so.1100(+0x17b5bb7)[0x7fed49842bb7]
   ```
   
   libarrow.so is mapped to 0x7fed4808d000:
   
   ```
   7fed4808d000-7fed484d7000 r--p 00000000 00:2c 2138445 
/usr/local/lib/python3.9/site-packages/pyarrow/libarrow.so.1100
   ```
   
   Subtracting the two, we're looking for 0x17b5bb7 in libarrow.so:
   
   ```
   $ objdump --demangle -d -T libarrow.so.1100
   ...
   00000000017b5b90 <Aws::Http::CurlHandleContainer::~CurlHandleContainer()>:
    17b5b90:    41 57                   push   %r15
    17b5b92:    49 89 ff                mov    %rdi,%r15
    17b5b95:    41 56                   push   %r14
    17b5b97:    41 55                   push   %r13
    17b5b99:    41 54                   push   %r12
    17b5b9b:    55                      push   %rbp
    17b5b9c:    53                      push   %rbx
    17b5b9d:    48 81 ec 08 02 00 00    sub    $0x208,%rsp
    17b5ba4:    e8 37 b3 f9 ff          callq  1750ee0 
<Aws::Utils::Logging::GetLogSystem()>
    17b5ba9:    48 85 c0                test   %rax,%rax
    17b5bac:    74 15                   je     17b5bc3 
<Aws::Http::CurlHandleContainer::~CurlHandleContainer()+0x33>
    17b5bae:    48 89 c5                mov    %rax,%rbp
    17b5bb1:    48 8b 00                mov    (%rax),%rax
    17b5bb4:    48 89 ef                mov    %rbp,%rdi
    17b5bb7:    ff 50 10                callq  *0x10(%rax)
   ...
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to