Why is `--wait-for` not attaching?

Subprojects LLDB
1

If, in bash, I invoke lldb --wait-for /var/lib/flatpak/app/com.github.Murmele.Gittyup/x86_64/stable/adfe463ee26a63bdaaa0af13f71e26bf9a925d37f43b4527c7b14625ab5a08a7/files/bin/gittyup, then, in another bash instance, invoke /var/lib/flatpak/app/com.github.Murmele.Gittyup/x86_64/stable/adfe463ee26a63bdaaa0af13f71e26bf9a925d37f43b4527c7b14625ab5a08a7/files/bin/gittyup, lldb doesn’t attach. Am I missing a step?

Context

I’m attempting to capture a coredump of /var/lib/flatpak/app/com.github.Murmele.Gittyup/x86_64/stable/adfe463ee26a63bdaaa0af13f71e26bf9a925d37f43b4527c7b14625ab5a08a7/files/bin/indexer, which is spawned by ./gittyup, to later be evaluated inside flatpak run --command=sh --devel com.github.Murmele.Gittyup, with gdb (because that’s all that is available there):

Environment

lldb-20.1.5-1.fc42.x86_64:

Name            : lldb
Epoch           : 0
Version         : 20.1.5
Release         : 1.fc42
Architecture    : x86_64
Installed size  : 25.4 MiB
Source          : llvm-20.1.5-1.fc42.src.rpm
From repository : <unknown>
URL             : http://lldb.llvm.org/
Vendor          : Fedora Project
2

try lldb --wait-for -n /your/process

We should probably make --wait-for without the name argument return an error..

1 Like
3
1 Like
4

@labath, thank you! That worked:

@JDevlieghere, thanks for the attribution. :grin: