Solved lldb is the trouble !

didier

Member

Reaction score: 12
Messages: 33

Hi everybody,

As said in title, lldb causes me some trouble.

Configuration:
  • Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz

  • FreeBSD 12.2-RELEASE-p1 GENERIC amd64

  • FreeBSD clang version 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611aa2)
    Target: x86_64-unknown-freebsd12.2
    Thread model: posix

  • lldb version 10.0.1 (git@github.com:llvm/llvm-project.git revision llvmorg-10.0.1-0-gef32c611aa2)
    clang revision llvmorg-10.0.1-0-gef32c611aa2
    llvm revision llvmorg-10.0.1-0-gef32c611aa2
clang and lldb, used are those from the base system.

Command p <variable> causes lldb to crash ... pitiably, always.

But take a look to this, instead, for instance :

Code:
$ cat main.c
int main(int argc, char* argv[])
{
    int cr = argc % 10;
    return cr;
}
$ cc -g main.c -o main

$ lldb main

(lldb) target create "main"
Current executable set to '/usr/home/didier/main' (x86_64).

(lldb) b main.c:4
Breakpoint 1: where = main`main + 32 at main.c:4:12, address = 0x00000000002018e0

(lldb) run
Process 49350 launching
Process 49350 launched: '/usr/home/didier/main' (x86_64)
Process 49350 stopped
* thread #1, name = 'main', stop reason = breakpoint 1.1
frame #0: 0x00000000002018e0 main`main(argc=1, argv=0x00007fffffffe450) at main.c:4:12
1 int main(int argc, char* argv[])
   2    {
3 int cr = argc % 10;
-> 4 return cr;
   5    }

(lldb) p cr
Program aborted due to an unhandled Error:
Error value was Success. (Note: Success values must still be checked prior to being destroyed).
Stack dump:
0.      Program arguments: lldb main
1.      HandleCommand(command = "p cr")
#0 0x0000000003b15cae (/usr/bin/lldb+0x3b15cae)
#1 0x0000000003b13f25 (/usr/bin/lldb+0x3b13f25)
#2 0x0000000003b165b0 (/usr/bin/lldb+0x3b165b0)
#3 0x00000008046c9b70 (/lib/libthr.so.3+0x14b70)
Abort trap (core dumped)


And you know what ? Error value was Success. 😄 Great ! Once in my life, I would have been witness of that.

Have some of you encountered this kind of trouble with lldb ? Not sure at all after having searched in the forum.

Anyway, any help is naturally welcome.

And thank you by advance for your contribution.

Cheers
Didier
 

mark_j

Daemon

Reaction score: 578
Messages: 1,053

LOL. :rolleyes:
My help: pkg install gdb. Problem solved.

Yes, lldb was not up to any standard in 12.2. One hopes it's substantially better in 13. (But install gdb anyway, because I predict lldb will still be junk in 13).
 
OP
D

didier

Member

Reaction score: 12
Messages: 33

LOL. :rolleyes:
My help: pkg install gdb. Problem solved.

Yes, lldb was not up to any standard in 12.2. One hopes it's substantially better in 13. (But install gdb anyway, because I predict lldb will still be junk in 13).
Tout simplement !

I didn't think one second that integrated lldb could be corrupted.
Great ! It works with gdb 👍 💪

Thank you a lot , Mark
Have a nice day
 

mark_j

Daemon

Reaction score: 578
Messages: 1,053

I can confirm with lldb v11 this bug has been fixed. Therefore, if that version is in FreeBSD 13, it should work as expected. (Well, at least for the example you sited, as complex as it was... ;):eek:)
I still wouldn't bet on lldb being able to totally replace gdb.
 
OP
D

didier

Member

Reaction score: 12
Messages: 33

Thank you again for your feedback, Mark.
A reason to upgrade FreeBSD, the next 13th.
I can confirm with lldb v11 this bug has been fixed. Therefore, if that version is in FreeBSD 13, it should work as expected. (Well, at least for the example you sited, as complex as it was... ;):eek:)
I still wouldn't bet on lldb being able to totally replace gdb.
 
Top