Date: Thu, 30 Oct 2014 16:03:34 +0000 From: Steven Hartland <killing@multiplay.co.uk> To: Ed Maste <emaste@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: HEADS UP: Standalone kernel debug files moving out of /boot/kernel/ Message-ID: <54526156.3080400@multiplay.co.uk> In-Reply-To: <CAPyFy2ApX-QDkfgc%2BjMBa9GfuzUhSL%2BHOP5O2kR70xODNb0Y_g@mail.gmail.com> References: <CAPyFy2APVUxpAztmWY-ux7gUZ7B8Qk65CLHV_fVYmxsazKgCPg@mail.gmail.com> <54511A7E.1020307@multiplay.co.uk> <CAPyFy2Bw9JH4w0iZ5hj2R1Ga9T4BZn_Z-8UBJ-jT6tmO%2Bi8VeA@mail.gmail.com> <20141030023224.GA42236@troutmask.apl.washington.edu> <5451A843.90805@multiplay.co.uk> <076D8745-53C6-4AFE-86D3-FF9B94F4EC76@emc.com> <54520177.5000008@multiplay.co.uk> <44A64906-CB05-4B52-A797-596D3A0DF897@emc.com> <EEFB6867-A317-4BEF-B219-D26ACDF9622E@lists.zabbadoz.net> <54523B57.1010802@multiplay.co.uk> <CAPyFy2BxfU2SAgkf-Bd1D_ZsgFsDSx=K=WvCKaPWqZ-1pkTm=A@mail.gmail.com> <54524A9F.8000400@multiplay.co.uk> <CAPyFy2ApX-QDkfgc%2BjMBa9GfuzUhSL%2BHOP5O2kR70xODNb0Y_g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30/10/2014 14:40, Ed Maste wrote: > On 30 October 2014 10:26, Steven Hartland <killing@multiplay.co.uk> wrote: >> Yer that's the process that was in my head, if debug symbols aren't >> available when savecore runs we're going to need a way to update / rerun >> when they are available, or even better give it the ability to do the same >> job with remote symbols? > Yeah, remote symbol support will be excellent (eventually). > > Crashinfo already operates on the most recent dump by default, so the > solution could be as simple as adding a flag to fetch debug files if > not already installed. The user would only need to run crashinfo -f to > regenerate the crash information with debug data available (and we > could mention that explicitly in the crash report). > >>> Setting DEBUGDIR= in /etc/src.conf will retain the current behaviour >>> of installing the debug data beside the kernel and modules (and >>> userland binaries and libraries). Does this adequately address your >>> use case? >> Yep that works :) > Great. > > I've been pondering this for so long that I may have forgotten not > everyone has the same context. > >> One thing to check would be to ensure that /usr is mounted when savecore >> runs. > Indeed, but we're covered there: the crash info is generated by > /usr/sbin/crashinfo, which relies on /usr/bin/gdb, so it better be > mounted :) Fantastic, thanks for taking the time to address my concerns, much appreciated :D
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54526156.3080400>