[all-commits] [llvm/llvm-project] 4581b0: [gsymutil] Verify output string table size and add...

[Roy Shi via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 4581b0890c33484f099d9c6a6d473192c97b976d
      https://github.com/llvm/llvm-project/commit/4581b0890c33484f099d9c6a6d473192c97b976d
  Author: Roy Shi <royitaqi at users.noreply.github.com>
  Date:   2026-02-17 (Tue, 17 Feb 2026)

  Changed paths:
    M llvm/lib/DebugInfo/GSYM/GsymCreator.cpp

  Log Message:
  -----------
  [gsymutil] Verify output string table size and address info offsets do not exceed 32-bit max (#181458)

Previously, https://github.com/llvm/llvm-project/pull/165940 fixed
llvm-dwarfdump and llvm-gsymutil so that they can correctly **consume**
>4GB dSYM. However, if the dSYM is large enough, `llvm-gsymutil` can
still **produce** invalid gSYM.

This change add validation into gsymutil, so that it will fail when the
output string table or address info offsets will exceed 32-bit max.

Similar to https://github.com/llvm/llvm-project/pull/165940, it may be
difficult to auto-test this change. For manual testing, I cannot find a
large enough dSYM for which the gSYM would hit the limits (I have a 9GB
dSYM which produces a 1.7GB gSYM). I'm open to ideas if anyone has any.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications