From owner-freebsd-current@freebsd.org Sun Feb 19 16:38:09 2017 Return-Path: Delivered-To: freebsd-current@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 4806FCE54E0 for ; Sun, 19 Feb 2017 16:38:09 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 28CE9C6D for ; Sun, 19 Feb 2017 16:38:09 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 28381CE54DF; Sun, 19 Feb 2017 16:38:09 +0000 (UTC) Delivered-To: current@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 27DFBCE54DE for ; Sun, 19 Feb 2017 16:38:09 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DCA13C6C for ; Sun, 19 Feb 2017 16:38:08 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-yw0-x22d.google.com with SMTP id v200so41076402ywc.3 for ; Sun, 19 Feb 2017 08:38:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Usd/FHpIR+9BLZc2iiclMxJr3bCpryRRXPNGKuBx0ds=; b=UotNmMDqcpyjMoUmr2O8kQxTOvWhYCBWlun4QOZZ73sfcjcmqmZC65xOAOGws64qXk 4LZU6+AR4Wbr8cLD09zMoWvs9t7UXaEUERugX36LPs99nhftwsd+IEA8YUh/40RgKYM1 lOZyA2lawFgDlosro+5ULKaOGR41ndH2AuWmQuAWPY6fD5Z5RS7IjqQ5wSM4QE3UlgkH yqD6xEwv6yIaSy7D6pLPAQ+WBcWLZRPi1Q9/JvQJD3Ix+TL24xEliFBDCIAwBa2KQpYx 7HsirFYenZqqLFPDURDAbTvBxIim2tUyKYWU3+XT7eldvjZl/rJDBQetC/G94H/n2osy qEDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Usd/FHpIR+9BLZc2iiclMxJr3bCpryRRXPNGKuBx0ds=; b=ei4vLJfJI9Yx90TNDZEip4slUg+w9IzNiyhiPhDc4n/yJWLNP/DCQ+3DwDcvPaEk9x qLApfAyHjDTr3qY056zFmv/cjfenmfk1CMnnXk4BnNahH8pNHMQy5WQY7v7SHCDVsi54 y9Tw39LJY/cGtgh7KxoVU11AzeIqa9CEekoKQBKHgPZidilp5/+ZE7QkCpQviX+kWu/t sYqq+9foZL3SMTKRhu4P8sNSW2UELq2WyOC1qXFogG5TzBLkbZ6J19aBtdC2LB/e5gbu qTVF1GrLa9wbpUeSw6FgfD3AXvAcrvdjq2eYA7t+rdVpAUtIo+IBgj6FN6pifObYcDdh 7UqQ== X-Gm-Message-State: AMke39nHukLKlvqKzGG7a6+dcDG7uVUDpvfv8jvaoY2QKeBJL+gMuFEMRdHz3xBrstWAs8zUxDRO/p9FSRsDLw== X-Received: by 10.129.154.194 with SMTP id r185mr13059329ywg.252.1487522286439; Sun, 19 Feb 2017 08:38:06 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.129.38.133 with HTTP; Sun, 19 Feb 2017 08:38:05 -0800 (PST) In-Reply-To: References: From: Alan Somers Date: Sun, 19 Feb 2017 09:38:05 -0700 X-Google-Sender-Auth: XuDT0OTMM88n2qgVGaSNeFn5jYc Message-ID: Subject: Re: GDB question [ at least at first... ] To: jbtakk@iherebuywisely.com Cc: current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Feb 2017 16:38:09 -0000 On Sun, Feb 19, 2017 at 1:33 AM, Jeffrey Bouquet wrote: > I've a custom kernel r313487 without, and > another with, debugging lines re-added. > [ i386 ] > > With daily vmcore in /var/crash from the > former, can the latter be used with GDB > [ the larger kernel ] to evaluate the > core file from the non-debugging, thinner > kernel? No. A debugging kernel isn't just a regular kernel with symbols. It also adds many more runtime assertions. The symbols from one won't match up with the core from another. > > And if so, better to learn GDB here or > send it off as an attachment to an > expert ?? There's never a bad time to learn GDB! It'll still work even on your non-debug kernel. You should try it out, and learn as much as you can. When you feel like you've gone as far as you can by yourself, then go ahead and post your problem to a mailing list of Bugzilla. Be sure to post the full stack trace. And search for it on Bugzilla before you post it; you may not be the first person to experience this bug. -Alan > > The crashes almost uniformly > [ 3/4 of them ] happen during > seamonkey or links -g, and also > after the > recent seamonkey upgrade > VS before, which almost > wrecked the install... if it matters any. > OR, the fixes I did to the almost-wrecked > install made it unstable to run > a browser within. OR, some sysctl > is not tuned to the recent hardware... > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"