Skip to content

Can't attach to Unity Mono Linux builds (6.1, 6.0, and 2018.3) #161

Closed

Description

@devek1

Module attach fails on the following games:
-DELTATRAVELER v3.0.13 Linux 64-bit (Unity 2018.3.14 Mono)
-DELTATRAVELER v3.0.13 Linux 32-bit (Unity 2018.3.14 Mono)
-DELTATRAVELER v3.1.0 Preview 6 Linux (Unity 6000.0.58 Mono, 64-bit)
-OFF Remake v1.2.1 Linux (Unity 6000.1.17 Mono, 64-bit)

Equivalent Windows builds of the same games running through Proton work fine.

Activity

  1. CryZe commented on Sep 18, 2026

    @CryZe
    Collaborator

    Which asr commit are you using, cause I'm in the middle of merging ero's work, some of which improving Linux support got merged just this morning.

  2. devek1 commented on Sep 18, 2026

    @devek1
    Author

    I've been continuously using cargo update to test the latest changes, I retested it just before opening this issue

    EDIT: slight correction, my last DELTATRAVELER tests were on commit 5021c43, so before the latest Mac changes but after all the Linux changes. OFF was tested on commit 6a0bbdc though

  3. ero-qt commented on Oct 11, 2026

    @ero-qt
    Contributor

    @devek1 could you try again on the latest asr? Linux Mono has per-build offsets now (#187) and the 64-bit games you listed should attach. I ran 2018.3, 6000.0 and 6000.1 Linux Mono players on it and they all read fine. One thing changed: attach_auto_detect needs the alloc feature now. The 32-bit DELTATRAVELER build still won't attach, because asr doesn't support 32-bit Linux Mono yet.

  4. devek1 commented on Oct 11, 2026

    @devek1
    Author

    I did clean builds for both with 54bb0f9 and they all still get stuck waiting on Module::wait_attach_auto_detect(&process).await

  5. ero-qt commented on Oct 11, 2026

    @ero-qt
    Contributor

    Thanks for trying again. I just ran a 6000.1.17f1 Linux Mono player, the same Unity version as OFF, on 54bb0f9 with wait_attach_auto_detect and it attached and read everything fine. So something in your setup must be different from mine.

    Which host are you running the splitter in, and which version? LiveSplit One, the OBS plugin or LiveSplit's auto splitting runtime? An older host might not find the Mono module by its file name.

    When Mono attaches, asr prints a line like mono: unity 6000.1.17.0 takes the build measured on 2021.2.0.61932. If you don't see anything like that, could you print what process.get_module_range("libmonobdwgc-2.0.so") returns for the game?

  6. devek1 commented on Oct 11, 2026

    @devek1
    Author

    I was using an asr-debugger manual build from a while back, but I rebuilt it now with all dependencies updated and that didn't help.

    the module ranges:
    DELTATRAVELER v3.0.13 - address 7f68cb800000, size 5619712
    DELTATRAVELER v3.1.0 - address 7fe622e00000, size 5951488
    OFF - address 7f6252e00000, size 5951488

  7. ero-qt commented on Oct 11, 2026

    @ero-qt
    Contributor

    Thanks, that helps. The OFF size matches the Mono library of my 6000.1.17f1 player exactly, so the debugger finds the module fine. Something after that fails on your machine.

    I also ran my 6000.1.17f1 player on the latest livesplit-core, which your rebuilt asr-debugger uses, and Mono attaches there too.

    Could you try attaching with the profile directly? This skips the Unity version lookup:

    use asr::game_engine::unity::mono::{profiles, Module};
    
    let module = Module::wait_attach(&process, profiles::UNITY_2021_2_0F1_LINUX_MONO_BDWGC_X86_64).await;

    If that attaches, the version lookup is the problem. If it still hangs, the output of the below command while OFF is running would help. Replace <pid> with the game's process ID:

    grep -E 'libmonobdwgc|UnityPlayer' /proc/<pid>/maps
  8. devek1 commented on Oct 11, 2026

    @devek1
    Author

    It still gets stuck

    The command output:

    22:20:19 in ~ ❯ grep -E 'libmonobdwgc|UnityPlayer' /proc/793295/maps
    7fd611200000-7fd6115a1000 r-xp 00000000 00:22 35839774                   /home/devek1/.local/share/Steam/ubuntu12_32/steamapps/content/app_3339880/depot_3339883/OFF_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
    7fd6115a1000-7fd6117a1000 ---p 003a1000 00:22 35839774                   /home/devek1/.local/share/Steam/ubuntu12_32/steamapps/content/app_3339880/depot_3339883/OFF_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
    7fd6117a1000-7fd6117ab000 r--p 003a1000 00:22 35839774                   /home/devek1/.local/share/Steam/ubuntu12_32/steamapps/content/app_3339880/depot_3339883/OFF_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
    7fd6117ab000-7fd6117ad000 rw-p 003ab000 00:22 35839774                   /home/devek1/.local/share/Steam/ubuntu12_32/steamapps/content/app_3339880/depot_3339883/OFF_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
    7fd618600000-7fd618d04000 r--p 00000000 00:22 35840384                   /home/devek1/.local/share/Steam/ubuntu12_32/steamapps/content/app_3339880/depot_3339883/UnityPlayer.so
    7fd618d04000-7fd61aad5000 r-xp 00704000 00:22 35840384                   /home/devek1/.local/share/Steam/ubuntu12_32/steamapps/content/app_3339880/depot_3339883/UnityPlayer.so
    7fd61aad5000-7fd61ab61000 r--p 024d5000 00:22 35840384                   /home/devek1/.local/share/Steam/ubuntu12_32/steamapps/content/app_3339880/depot_3339883/UnityPlayer.so
    7fd61ab61000-7fd61ab7d000 rw-p 02561000 00:22 35840384                   /home/devek1/.local/share/Steam/ubuntu12_32/steamapps/content/app_3339880/depot_3339883/UnityPlayer.so
    
  9. ero-qt commented on Oct 11, 2026

    @ero-qt
    Contributor

    Thanks. Those lines match the layout of the library in my 6000.1.17f1 player, so it's loaded normally.

    Both ways of attaching then do the same thing. On Linux, they read the Mono library's symbols to find mono_assembly_foreach. Could you run this while the game is running and send what it prints?

    let base = process.get_module_address("libmonobdwgc-2.0.so").unwrap();
    asr::print_limited::<128>(&format_args!("read {:?}", process.read::<[u8; 4]>(base)));
    asr::print_limited::<128>(&format_args!("symbols {}", asr::file_format::elf::symbols(&process, base).count()));

    On my 6000.1.17f1 player it prints read Ok([127, 69, 76, 70]) and symbols 2546.

  10. devek1 commented on Oct 11, 2026

    @devek1
    Author

    Oh it was a permission issue, I forgot about the matter of permissions because for Proton games they aren't needed.
    Running asr-debugger with sudo or giving it SYS_CAP_PTRACE fixed this for me and gives the same results you list here for OFF. Both 64-bit Deltatraveler versions also worked.
    (the initial attempt gave read Err(error) and symbols 0)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions