3 ms·

Oops, that's not a good trade-off; does it always take that long when you start LeanCreator on your machine, or was it - as I would expect - only the first time

by Rochus 4y ago

Oops, that's not a good trade-off; does it always take that long when you start LeanCreator on your machine, or was it - as I would expect - only the first time it required to locate the debugger? If it repeats with each start I should add an option to disable this search or reduce the timeout. Can you try whether it also takes that long if you directly start lldb on the command line?

andai 4y ago
lldb starts instantly. For LeanCreator, the delay is there every time: I just used a stopwatch, it was at least 31 seconds.
- Rochus 4y ago
  Ok, I see, but apparently LeanCreator hangs when accessing your toolchain and consequently also cannot use it to build anything; either there is an installation issue with the toolchain or an incompatibility with LeanCreator which I don't know yet. The 30 secs are probably the timeout in LeanCreator when trying to run an executable of the toolchain. Which version of Clang/lldb have you installed? Have you also MSVC or MingW installed on your machine?
  - andai 4y ago
    Yeah, all three. GCC 12.1.0 (MSYS2) LLVM 15.0.7 MSVC 19.33.31630 (not on PATH) (This thread's probably getting too long, you can reach me at my email address. See my HN profile.)
    - Rochus 4y ago
      Maybe there is compatibility issue with lldb; I already found an issue with the recent lldb version on Mac M1 (see https://github.com/rochus-keller/LeanCreator/issues/1 https://github.com/rochus-keller/LeanCreator/issues/1). You could try to tempoarily rename the clang/lldb directory so LeanCreator doesn't see it anymore at startup.
    - Rochus 4y ago
      I will organize a recent Windows machine with newest versions of these tools and test/debug there myself (https://github.com/rochus-keller/LeanCreator/issues/3 https://github.com/rochus-keller/LeanCreator/issues/3).
    - Rochus 4y ago
      Have you received my email? There is a new version of LeanCreator which also detects recent MSVC versions.

by Rochus 4y ago

andai 4y ago

lldb starts instantly. For LeanCreator, the delay is there every time: I just used a stopwatch, it was at least 31 seconds.

Rochus 4y ago
Ok, I see, but apparently LeanCreator hangs when accessing your toolchain and consequently also cannot use it to build anything; either there is an installation issue with the toolchain or an incompatibility with LeanCreator which I don't know yet. The 30 secs are probably the timeout in LeanCreator when trying to run an executable of the toolchain. Which version of Clang/lldb have you installed? Have you also MSVC or MingW installed on your machine?
- andai 4y ago
  Yeah, all three. GCC 12.1.0 (MSYS2) LLVM 15.0.7 MSVC 19.33.31630 (not on PATH) (This thread's probably getting too long, you can reach me at my email address. See my HN profile.)
  - Rochus 4y ago
    Maybe there is compatibility issue with lldb; I already found an issue with the recent lldb version on Mac M1 (see https://github.com/rochus-keller/LeanCreator/issues/1 https://github.com/rochus-keller/LeanCreator/issues/1). You could try to tempoarily rename the clang/lldb directory so LeanCreator doesn't see it anymore at startup.
  - Rochus 4y ago
    I will organize a recent Windows machine with newest versions of these tools and test/debug there myself (https://github.com/rochus-keller/LeanCreator/issues/3 https://github.com/rochus-keller/LeanCreator/issues/3).
  - Rochus 4y ago
    Have you received my email? There is a new version of LeanCreator which also detects recent MSVC versions.