The LLDB Debugger • Hacker News Board

Re: The LLDB Debugger

#31

Post by krakensden » Wed, Jun 09, 2010, 7:51 AM UTC

CountSessine wrote: post #27

jrockway wrote: post #21

Earlier quoted context omitted.

"step" to step, "backtrace" to get a backtrace, ...? Yeah, that's confusing.

"step" and "backtrace" of course being the only possible logical names for those functions. Not having memorized the gdb info pages, I would never mistakenly type in "next" or "over" or "in" or "stack" or "stackframe" or "frame" or...

So use a gui like Nemiver if you don't want to deal with a cli.

Re: The LLDB Debugger

#32

Post by wingo » Wed, Jun 09, 2010, 8:16 AM UTC

pbiggar wrote: post #29

I would say that gdb can never be as good as lldb can be, simply for C++ expression parsing (unless they integrated the gcc parser).

I believe the plan is for gcc to provide a build server to which the debugger could ask, "expand this expression for me please".

Re: The LLDB Debugger

#33

Post by wendroid » Wed, Jun 09, 2010, 1:57 PM UTC

alec wrote: post #7

yan wrote: post #2

Hopefully this replaces GDB, and good riddance.

GDB 7.1 is a great improvement over previous versions and has a lot of the features LLDB intends to have - better C++ support, better thread debugging, more accurate backtraces, and a Python scripting API - as well as some features that aren't on the LLDB roadmap yet, like tracepoints for debugging time-sensitive code and multi-program debugging. You should check it out if you're unhappy with an older version.

whatever, still shit, take a look at a proper debugger

http://doc.cat-v.org/plan_9/4th_edition/papers/acidpaper

Re: The LLDB Debugger

#34

Post by lallysingh » Wed, Jun 09, 2010, 2:35 PM UTC

ramchip wrote: post #26

lallysingh wrote: post #19

Earlier quoted context omitted.

Apple employs a few (more than 1?) LLVM people, but it's hardly an Apple project by any means. LLVM is a substantial and fantastic project. At the basis, it's a compiler backend in-a-box. Additional projects, like clang and this, are providing a modern compiler platform for us, finally. gcc & friends have made great advances, relative to other compilers, but they all do suck. It's been 12 years and I still can't use…

I've found the Visual Studio debugger to be very nice, actually. It shows STL classes in an intelligible way, and the IDE integration is (as expected) excellent. Unfortunately OSS alternatives are still a lot less intuitive, and VS is stuck to Windows.

I was actually talking about the VS debugger. If you get even a little fancy with templates & metaprogramming, the whole thing is just terrible.

Re: The LLDB Debugger

#35

Post by surki » Wed, Jun 09, 2010, 4:13 PM UTC

pbiggar wrote: post #28

jrockway wrote: post #21

Earlier quoted context omitted.

"step" to step, "backtrace" to get a backtrace, ...? Yeah, that's confusing.

When you try to do complicated stuff it does get confusing. Like remembering the exact way you need to type out C++ method names (you need to put single-quotes in just the right places.)

Which version are you running?

I am on 6.8.50.20081120-cvs I seem to have auto completion (on tab)

Re: The LLDB Debugger

#36

Post by pbiggar » Wed, Jun 09, 2010, 6:50 PM UTC

surki wrote: post #35

pbiggar wrote: post #28

Earlier quoted context omitted.

When you try to do complicated stuff it does get confusing. Like remembering the exact way you need to type out C++ method names (you need to put single-quotes in just the right places.)

Which version are you running? I am on 6.8.50.20081120-cvs I seem to have auto completion (on tab)

It does have tab completion, but it doesn't work well. I think you need to open the quote to tab complete (in C++, using namespaces or class names), but it seldom does what you want.

I've seen this since about 6.7, I last used 7.1.