tadeja commented on issue #49767:
URL: https://github.com/apache/arrow/issues/49767#issuecomment-4547806382

   Summary of findings: Ubuntu 24.04 apt mold version 2.30.0 has a 
non-determinism bug 
([rui314/mold#1247](https://github.com/rui314/mold/issues/1247), fixed in [mold 
version 2.31.0](https://github.com/rui314/mold/releases/tag/v2.31.0)). In our 
case, mold's output sometimes placed gRPC-bundled proto descriptors into 
`.rodata` (read-only) while emitting `R_X86_64_RELATIVE` relocations against 
them, so ld-_.so couldn't apply those at startup.
   
   Full diagnostic trail on [fork debug 
branch](https://github.com/apache/arrow/compare/main...tadeja:arrow:49767-flight-sql-sigsegv):
 [libc6-dbg-symbolized 
backtraces](https://github.com/tadeja/arrow/commit/6dcdc026bd9ac1388dc5a3717e2662d1bddce0ba),
 [relocation-locator 
script](https://github.com/tadeja/arrow/commit/53eaa29d8271208b2b7184b8308bb5e0d8928d5a),
 and earlier workarounds 
([-no-pie](https://github.com/tadeja/arrow/commit/54d2a30aeaf911ac71a29243faa0ba7a53bc72ac),
 
[mold=OFF](https://github.com/tadeja/arrow/commit/6732ef45add327f0559133f7f90d9564b4eec996),
 [mold 2.31 from 
tarball](https://github.com/tadeja/arrow/commit/d51c91c1de86b2be69c432f46b468d4e11024fc5),
 [mold 2.37 from 
.deb](https://github.com/apache/arrow/pull/50033/changes/c2db4fac285e895ee240b9d59ad5883b6dfcdf3e))
 before landing on @kou's suggestion [see pr 
changes](https://github.com/apache/arrow/pull/50033/changes)).
   
   [Ubuntu mold versions](https://repology.org/project/mold/versions) for 
Ubuntu 22.04: 1.0.3, Ubuntu 24.04: **2.30.0**, (and newest LTS Ubuntu 26.04: 
2.40.4).
   <img width="225" height="250" alt="Ubuntu mold versions" 
src="https://github.com/user-attachments/assets/159fde76-e644-4e69-9c00-220534432eef";
 />
   
   Two PRs ready for review: #50033 to close this issue
   and mini debug #50034 (to address #49776)


-- 
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