You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "lidavidm (via GitHub)" <gi...@apache.org> on 2023/04/28 02:36:39 UTC

[GitHub] [arrow-adbc] lidavidm opened a new issue, #616: c: Windows builds failing with `Exit code 0xc0000374` (heap corruption)?

lidavidm opened a new issue, #616:
URL: https://github.com/apache/arrow-adbc/issues/616

   Might have started around #597?


-- 
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: issues-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow-adbc] lidavidm commented on issue #616: c: Windows builds failing with `Exit code 0xc0000374` (heap corruption)?

Posted by "lidavidm (via GitHub)" <gi...@apache.org>.
lidavidm commented on issue #616:
URL: https://github.com/apache/arrow-adbc/issues/616#issuecomment-1533103209

   I think for now I'll switch things to use release mode; we may want to see if we can get this fixed upstream in the conda package + we should stop relying on gmock now that the two packages are combined.


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow-adbc] lidavidm commented on issue #616: c: Windows builds failing with `Exit code 0xc0000374` (heap corruption)?

Posted by "lidavidm (via GitHub)" <gi...@apache.org>.
lidavidm commented on issue #616:
URL: https://github.com/apache/arrow-adbc/issues/616#issuecomment-1533102317

   Interestingly it passes in release mode.
   
   Reverting to the commit before #597 does not help so it's unrelated. 
   
   I see in the last passing build we have gtest `h91493d7_0` and in the first failing `h91493d7_1`. Among other things, that bump changed gtest from static libraries to DLLs. Installing the old package fixes things.
   
   With the old package CMake prints
   
   ```
   -- Found GTest: C:/Users/User/mambaforge/envs/adbc/Library/lib/gtest-md.lib
   ```
   
   And the new package:
   
   ```
   -- Found GTest: C:/Users/User/mambaforge/envs/adbc/Library/lib/cmake/GTest/GTestConfig.cmake (found version "1.13.0")
   ```
   
   The old package contains both debug and release versions of DLLs, but not the new version.
   
   ```
   Library/bin/gtest_dll-md.dll
   Library/bin/gtest_dll-mdd.dll
   Library/bin/gtest_dll.dll
   Library/bin/gtest_dlld.dll
   ```
   
   in the old package, vs the new package:
   
   ```
   Library/bin/gmock.dll
   Library/bin/gmock_main.dll
   Library/bin/gtest.dll
   Library/bin/gtest_main.dll
   ```


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow-adbc] lidavidm closed issue #616: c: Windows builds failing with `Exit code 0xc0000374` (heap corruption)?

Posted by "lidavidm (via GitHub)" <gi...@apache.org>.
lidavidm closed issue #616: c: Windows builds failing with `Exit code 0xc0000374` (heap corruption)?
URL: https://github.com/apache/arrow-adbc/issues/616


-- 
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: issues-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org