search

freedib / lldbmi2

A simple MI interface to LLDB for Eclipse
Other
47 stars 16 forks source link

Could not determine LLDB version using command: /usr/local/bin/lldbmi2 --version #32

Closed DengueTim closed 2 years ago

DengueTim commented 2 years ago

Hi, I get the error below on an M1 mac with MacOS 12.2, xcode command line utils 13.4, Eclipse IDE for C/C++ (20220908-1902)

gcc and a few other packages are installed via Homebrew, but not gdb. not sure if that is a factor.

Could not determine LLDB version using command: /usr/local/bin/lldbmi2 --version
Unexpected output format: 

GNU gdb (GDB) 7.7.1
lldbmi2 version 1.1.166

CMake gives:

Scotty:build tp$ cmake ..
-- The C compiler identification is AppleClang 13.1.6.13160021
-- The CXX compiler identification is AppleClang 13.1.6.13160021
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
LLDB_LIBRARY:/Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework @  ^ /Library/Developer/CommandLineTools/Library/PrivateFrameworks
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/tp/src/lldbmi2/build

Have I done something wrong?

freedib commented 2 years ago

Can you check closed issue #30 How to use with Eclipse on Mac, 7th comment? You probably configured LLDB-MI Debug Process Launcher in Debugger tab of Debug configuration. You must use default GDB (DSF) Debug Process Launcher

DengueTim commented 2 years ago

Thanks. That works, although inspecting variables still has some problems. I got the impression this is to do with llvm. Do you know if there is any difference between using Apple's clang or using the version through Homebrew?

freedib commented 2 years ago

I don't think it would make a difference. The problem is more that lldb is (or was (7 years ago when I make this app)) more limited than gdb when inspecting variables. lldbmi2 tries to make translation from gdb syntax to lldb syntax, but it could be improved. Could you give me an example of variables not showing correct values? (variable declaration and expression to show variable content). Also, did you try lldb-mi? I'm curious about its progress

DengueTim commented 2 years ago

Hi, I tried with lldb-mi too. It had similar issues with some variables not showing up. I've actually given up on using Eclipse CDT with llvm on mac. The issue is mainly Eclipse I think, but I don't have the time to dig into the problems and find solutions.

kenroser commented 2 years ago

On 10/24/22 9:53 AM, DengueTim wrote:

Hi, I tried with lldb-mi too. It had similar issues with some variables not showing up. I've actually given up on using Eclipse CDT with llvm on mac. The issue is mainly Eclipse I think, but I don't have the time to dig into the problems and find solutions.

— Reply to this email directly, view it on GitHub https://github.com/freedib/lldbmi2/issues/32#issuecomment-1289071521, or unsubscribe https://github.com/notifications/unsubscribe-auth/AELWOX3UE56ABHGM3X333UDWE2IFLANCNFSM6AAAAAARJBLC7A. You are receiving this because you are subscribed to this thread.Message ID: @.***>

I too have given up on Eclipse on the Mac ( or Linux ).  Eclipse has too much trouble with modern C++ code.  I've moved on to VSCode (free) and CLion ($), both of which have excellent Mac support.