Pranav2612000 commented on issue #3840:
URL: https://github.com/apache/arrow-adbc/issues/3840#issuecomment-3695722864
> (1) are you sure your IDE isn't automatically entering the debugger on a
crash and causing your application to "hang"?
I guess the EXEC_BAD_ACCESS error we see is due to the IDE. In the stuck
state, pressing the "Continue program" button prints this message in the
console. I'm sure the IDE is not causing the "hang" because the behaviour is
the same when I run it through ITerm
> (2) this seems to be related to thread-locals, are you using those?
No. Although we do use tokio, I'm wondering if that could be causing this
issue ( that's a difference between the example which works and the test which
doesn't )
> (3) how were you able to conclude this is related to ADBC?
I'm able to reproduce the issue with a very simple test ( shared above ).
Commenting out the part which loads the driver works and the test exits. Using
different driver ( tried with bigquery ) also has the same "stuck/hang"
behaviour. Added sample `panic!` in the `adbc` codebase to debug the issue.
Whenever the init `FFI_AdbcDriverInitFunc` runs, ( [this
line](https://github.com/apache/arrow-adbc/blob/4a3b8eb940a138a7517fbdcf43d7b53692db5130/rust/driver_manager/src/lib.rs#L425)
)the test goes into this state. ( Adding a panic immediately before this line
doesn't cause a hang, but adding a panic immediately after causes the hang )
Let me look at all the threads once again, to see if I see anything
interesting. By the way, Thank you for your help @lidavidm and the prompt
replies 😄
--
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]
