From owner-svn-src-all@freebsd.org Wed Apr 19 23:10:42 2017 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7828D46E78 for ; Wed, 19 Apr 2017 23:10:42 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from nm20-vm3.bullet.mail.ne1.yahoo.com (nm20-vm3.bullet.mail.ne1.yahoo.com [98.138.91.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9B7EAA5D for ; Wed, 19 Apr 2017 23:10:42 +0000 (UTC) (envelope-from pfg@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1492643043; bh=Ylh2uWd2AlgrVqzIRIdy5qw5FZHRGZnUoxOaZjrbHHs=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From:Subject; b=E+1Sr40bNo+BQnAuW6neBfW0TSrloKCY3vJk+r8uHuKe0yOyjVBJX1/vrtF1eJ2kwyZLiMrgZzE4IOlNykjr9avpDtC0yr9GLBFI1NveqXCIZDd+YlpxLrget4WPqeoSuL6Ocpetxds6gpGkhuw9aGyK8ugTQP9iZRiI25YK1EuPPcClzMW39jaiAr7Yc3m4bC0qkzser2Mrp9sJEzGf3SUCgl7wGq3fFZGVknxewfzQILGRMSpUBgmK6TMZpsv+zDwsui3CIk5Xbxa0TysA7PUy7763opg6wXZAj2YCjb0ojjQg0mO+Vtw/aXe+jiZASdYjF93HO1x/UR2fP80POA== Received: from [98.138.226.179] by nm20.bullet.mail.ne1.yahoo.com with NNFMP; 19 Apr 2017 23:04:03 -0000 Received: from [98.138.84.45] by tm14.bullet.mail.ne1.yahoo.com with NNFMP; 19 Apr 2017 23:04:03 -0000 Received: from [127.0.0.1] by smtp113.mail.ne1.yahoo.com with NNFMP; 19 Apr 2017 23:04:02 -0000 X-Yahoo-Newman-Id: 988610.30654.bm@smtp113.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: Tf1OaFEVM1mI3sr8oeobJPjiCxPbcbAD9RcqWVU3sdIj21d tjmd9ndKf5HKKPig.qnjl66eqgYK3jbUUYplyVhtShbWpmoCPoLB5TgBauVZ u_m3ILzPQE4tQjfDTm0RVEU7hNr.nChLEuZMSRjvcjKBUDrTUIwK.WFv_ylv rr84oPuM3un6.acc.byy4mz0Wj_i0lqzaTpsLLs4vXd200xbQlFe75.NYqf0 .l_xMBQkduipnRB5koSrWPV.5QKNInM_w9KS5fF9IbNGJYTCFFZsyJZuHQFJ K7uX4jhPD70eYasMvYwTrtESbvW1g1Syl8YIrMtbZv3e7CqbWqzG.iWgghR8 axP_8uE1liqbZ8b63Sr5lvNzDIHRkTE6eEZF0ryXIcNT3bZOvmsDID4Pmfvi klId1lDR.rf0Dd158OWZ60xo58Ap04GoHYQX9renx.ZOC_UJrPHPZP4Rj_1I .h76UJQbW7d_GE1FnhjKBn0R0SqHc_p7W3Gpr1jOyl09YNJ4HaOGPPLJ9hDS WvrUz9bWi5MViShCarhEAO7wZv21YSIQXNDjiGpoJ3YTD X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf Subject: Re: svn commit: r317094 - head/share/mk To: rgrimes@FreeBSD.org, Eric van Gyzen References: <201704192218.v3JMIYtS032774@pdx.rh.CN85.dnsmgr.net> Cc: John Baldwin , Slawa Olhovchenkov , svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org From: Pedro Giffuni Organization: FreeBSD Project Message-ID: Date: Wed, 19 Apr 2017 18:04:12 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <201704192218.v3JMIYtS032774@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 23:10:42 -0000 On 19/4/2017 17:18, Rodney W. Grimes wrote: > [ Charset windows-1252 unsupported, converting... ] >>>>>>> Generating core.txt now complety broken? >>>>>> No. crashinfo has supported gdb from ports for quite a while now. >>>>>> If you 'pkg install gdb' crashinfo defaults to using the ports gdb over >>>>>> the base one already. >>>>> I am about clean install, w/o ports. >>>> Until we get some sort of klldb support that will not work. However, >>>> we already have platforms now where /usr/bin/gdb doesn't work for that. >>>> riscv and aarch64 aren't supported in ancient gdb, and the MIPS >>>> /usr/bin/gdb didn't really work for me in my testing. >>> So we break what worked on a Tier1 Platform? With my "user" hat on >>> these are the exact kind of breakages that send me looking for another >>> platform to run on. We far to often just go oh you can do X y and Z >>> to get around what we broke forgetting that the user 6 months from now >>> when this hits a release isnt gona come ask, he may just go down the >>> road to something else. >>> >>> Remove gdb WHEN klldb can replace it, not a day before. Using "oh its >>> broken on aarch64 and mips" is not a reason to break things on i386/amd64. >>> >>> Yes, I know we want to get gnu stuff out of the tree, but that needs >>> to come AFTER a proper replacement is avaliable. >>> >>>>> Also, how to generate core.txt after crash, reboot and install gdb >>>>> from ports? (port instaled after crash) >>>> You can always run crashinfo by hand. >>> /me starts to look for a new OS, this one is not very good at user support. >> # crashinfo >> Please install GDB and run 'crashinfo' again. >> The easiest way to install GDB is: pkg install gdb >> Unable to find matching kernel for /var/crash/vmcore.1 >> >> https://reviews.freebsd.org/D10429 >> >> This should be good enough to keep the user from looking for a new OS. >> It also gets a much better version of GDB onto the box, which will make >> the user happier than giving them an ancient one and letting them flail >> around with it for a while before learning that they should install a >> newer one. > Actually this is exactly what I would expect from Linux! Does linux include a kernel debugger now? Last I heard Linus was against debuggers, just as he was once against version control ... and Codes of Conduct. > Why do we need to pull the trigger on GDB other than to pull the trigger > to say we are GPL free, if that is the reason then this is the wrong > way to go about it. Well, one of the reasons may be that we need a debugger that supports newer DWARF. At some time we started hacking our llvm to not use a recent dwarf versions(4?). Pedro.