• Status Unconfirmed
  • Percent Complete
  • Task Type Bug Report
  • Category Packages → Packages: Staging
  • Assigned To No-one
  • Operating System i686
  • Severity High
  • Priority Very Low
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Arch Linux 32
Opened by Anthony Eden - 26.04.2020

FS#108 - lldb fails to run any binary (error: failed to launch or debug process)

Very easy to reproduce. lldb version 10.0.0, just try to run any binary.

[aeden@arch32 bin]$ lldb $(which date)
(lldb) target create “/usr/bin/date” Current executable set to ‘/usr/bin/date’ (i386).
(lldb) run
error: failed to launch or debug process

Andreas Baumann commented on 28.04.2020 11:19

I have 9.0.1 on pentium4/stable, which also doesn't work. So confirmed. :-)

Anthony Eden commented on 28.04.2020 19:54

Does this seem like an upstream bug?

Andreas Baumann commented on 29.04.2020 04:36

64-bit works. Then I rebuilt lldb 10, but now it depends on llvm 10, compiler-rt 10.
I refrain to force-move llvm/clang 10 to stable, as this has the potential to
break things.

Andreas Baumann commented on 30.04.2020 15:02

This is just bad error handling:

  if (!m_process_sp) {
    if (error.Success())
      error.SetErrorString("failed to launch or debug process");
    return error;

What is the underlying operating system error here..

It still happens with llvm 10, lldb rebuilt in testing, both i686/pentium4.

Andreas Baumann commented on 30.04.2020 15:09

strace tells me (when typing run):

[pid   589] ioctl(0, SNDCTL_TMR_STOP or TCSETSW, {B38400 opost isig icanon echo ...}) = 0
[pid   589] clock_gettime64(CLOCK_MONOTONIC, {tv_sec=22702, tv_nsec=900673854}) = 0
[pid   589] brk(0x1c9d000)              = 0x1c9d000
[pid   589] clock_gettime64(CLOCK_MONOTONIC, {tv_sec=22702, tv_nsec=904100916}) = 0
[pid   589] write(2, "error: failed to launch or debug"..., 41error: failed to launch or debug process
) = 41

Not really helpful..

Anthony Eden commented on 08.05.2020 18:23

I tried lldb on debian testing (i386), and it similarly is not able to launch process.

Andreas Baumann commented on 14.05.2020 13:32

Thanks for posting the bug upstreams. :-)


Andreas Baumann commented on 15.05.2020 12:54

I'm debugging lldb with gdb and I see that there is simply no proccess plugin available
for the platform.

I also see a weird architecture triplet:

$3 = (const lldb_private::ArchSpec &) @0x58f540: {m_triple = {
    Data = "i386--linux", Arch = llvm::Triple::x86, 
    SubArch = llvm::Triple::NoSubArch, Vendor = llvm::Triple::UnknownVendor, 
    OS = llvm::Triple::Linux, Environment = llvm::Triple::UnknownEnvironment, 
    ObjectFormat = llvm::Triple::ELF}, 
  m_core = lldb_private::ArchSpec::eCore_x86_32_i386, 

This looks highly untested for 32-bit Intel if not said unimplemented..


Available keyboard shortcuts


Task Details

Task Editing