Apple Silicon - ODBC Driver Crash

Question

Created Feb ’21

Replies 2

Boosts 0

Views 1.2k

Participants 2

Hi,

I am trying to connect to Snowflake DB via ODBC (to use it with Tableau) but Tableau seems to crash. After some investigation, I realized the issue is not Tableau but ODBC connection and iodbctest is failing due to "7295 illegal hardware instruction iodbctest".

Attaching logs:

Logs

This is a blocker for me to switch my workflow completely to M1. Any advice on a workaround or a solution will be appreciated.

Thanks.
/M

Answered by DTS Engineer in 662322022

Crashes like this usually indicate that the code trapped, that is, it deliberately crashed because it detected some internal inconsistency check. The crashing frame strongly suggests that this is within C++ constructor the Snowflake library:

Code Block  0   libSnowflake.dylib … _GLOBAL__sub_I_base64.cpp + 6
1   dyld               … ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 559

Is this your code? If not, you should talk to the author to see if they have any suggestions as to what’s gone wrong.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

Feb ’21

Accepted Answer

Crashes like this usually indicate that the code trapped, that is, it deliberately crashed because it detected some internal inconsistency check. The crashing frame strongly suggests that this is within C++ constructor the Snowflake library:

Code Block  0   libSnowflake.dylib … _GLOBAL__sub_I_base64.cpp + 6
1   dyld               … ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 559

Is this your code? If not, you should talk to the author to see if they have any suggestions as to what’s gone wrong.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"

1

Answer 2

fasih58 OP

Feb ’21

Thank you @eskimo. Snowflake fixed their ODBC driver and version 2.22.5 seems to work fine. The issue was with v2.22.4.

0