From owner-freebsd-toolchain@FreeBSD.ORG Mon Jul 7 19:27:17 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 066E278E; Mon, 7 Jul 2014 19:27:17 +0000 (UTC) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 56F8027EC; Mon, 7 Jul 2014 19:27:16 +0000 (UTC) Received: by mail-lb0-f169.google.com with SMTP id l4so3266430lbv.28 for ; Mon, 07 Jul 2014 12:27:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=b+/FFFsR8BRBG/0W9ny0b52RXMMUiAX68WMH/lb4w0g=; b=xcS+W4+hX6RYN0gZ6dfzi8ghWMnqrmjL1MIypnPeFLVJCGzBlsD7gE6y0PMYZbA6FP bK8tEjmjf5WWzqvbfJ7Hwhp2K+/UffDtFYNamkIgmINYTz7yBj9uncLLEpZVTf2vXM65 1/6NLCvJ8GoF8UIbQl0DHC254L0tz9laXRlg36momWTig7Jdy0/Z3jdsbTPfyakpHk7B fSdz43xZEKOjGvjDI2uF8CS/ZBFQ29PZe2SzigPWxxmvz1gii5vzZKdIXER/u0N2CMid Fil5UiwfinA9TdPQ9ASN+BgcCFWVjzaoBsDO29/GKFWGgPSbQlJ/cocKWUXXIfKBp/Hs oTBA== MIME-Version: 1.0 X-Received: by 10.152.204.102 with SMTP id kx6mr24963582lac.32.1404761234181; Mon, 07 Jul 2014 12:27:14 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.67.71 with HTTP; Mon, 7 Jul 2014 12:27:14 -0700 (PDT) In-Reply-To: References: Date: Mon, 7 Jul 2014 12:27:14 -0700 X-Google-Sender-Auth: WMe1-smUK4mJnJHtX3wKFg9oa5g Message-ID: Subject: Re: gdb in CURRENT cannot debug userland cores, when is kernel lldb coming? From: Craig Rodrigues To: Ed Maste Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2014 19:27:17 -0000 Ed, Can we enable WITH_LLDB=yes by default in CURRENT only? It took me a while to figure out that I needed to build/install lldb to debug some of my coredumps in CURRENT. I realize that things are in motion with respect to the toolchain, but it is annoying that in CURRENT, we have a debugger in the base system that cannot debug userland cores properly. I realize that things are in motion with respect to the toolchain, but this will help. I really hope that the Summer of Code project to implement kernel debugging support for lldb reaches completion and we can finally remove our ancient gdb from base (at least in CURRENT). Thanks. -- Craig On Wed, Jun 11, 2014 at 11:53 AM, Craig Rodrigues wrote: > Hi, > > Recently when trying to debug some coredumps in CURRENT from > a userland process in the devel/libvirt port, I found that the gdb in > base could not get a backtrace from the core file: > > > http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-June/002606.html > > I needed to add to my /etc/src.conf WITH_LLDB=yes > and compile and install lldb, which *could* analyze the coredump. > > I realize that gdb in base is on its way out the door, and that > clang and lldb are the new world order. However, one of the > main blockers for removing gdb from base is that > there is no equivalent to kgdb in the lldb world. > > Is anyone working on a kernel lldb? When is it expected to be ready? > Will something like it be ready by end of 2014? > > Even though this may not be an issue in the stable/10 branch, > it would be nice to have a kernel lldb debugger ready by > the next 10.1R if possible. > > -- > Craig >