Re: how to interpret crash?

From: Robert Watson (rwatson_at_freebsd.org)
Date: 05/28/04

  • Next message: David Magda: "Re: how to interpret crash?" 
    Date: Thu, 27 May 2004 19:55:48 -0400 (EDT)
To: David Magda <dmagda@ee.ryerson.ca>

    On Thu, 27 May 2004, David Magda wrote:

    > > You don't need the actual kernel.debug to boot with, just the image
    > > around
    > > so when you run gdb -k it can pull the symbols out. Otherwise, the
    > > installed kernel is stripped. On -CURRENT, there's a
    > > /sys/$arch/compile/$kernelname.debug that you suck in.
    >
    > Yes, but I sometimes clean out my compile / object directory and so when
    > I need the debugging kernel it's not there (and I may have cvsup'ed my
    > source tree). It would be nice if a debugging kernel is sitting there
    > beside the kernel that I booted.

    I've you've cvsup'd your source tree, the debugging kernel may not be all
    that useful either, as the goal of the debugging symbols is to provide a
    mapping from locations in the kernel binary to locations in the kernel
    source code. If you have the same source code and same config file, there
    should be little variation in the compiled code and typically building a
    fresh kernel from the same pieces is sufficient to provide you everything
    you need. If you've cvsup'd and no longer have the source code for the
    old kernel, regardless of having debugging symbols, you're in a much worse
    starting point for tracking down the problem.

    One important reason that the debugging kernel isn't kept around is space
    considerations: in -CURRENT, a 5mb kernel will generally be accompanied by
    a 30mb debugging kernel. Each module with symbols is similarly swollen:
    the agp module is normally 72k, but with debugging symbols is 368k. It
    doesn't take too much of that to fill up most root partitions...

    I don't debate your basic point that on a stable system, you're least
    likely to find the symbols when you most need them, as the system will run
    fine for a long time and then run into some edge case, unusual hardware
    failure mode, or whatever, and given that it's been stable for years, you
    will find yourself with little debugging recourse. That's where tricks
    like using nm to track down the symbols, turning on dumps by default,
    compiling with the necessary DDB bits to generate a stack trace, etc, can
    come in quite handy.

    Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
    robert@fledge.watson.org Senior Research Scientist, McAfee Research

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: David Magda: "Re: how to interpret crash?"

    Relevant Pages

    • Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
      ... source code for the part of their Linux kernel images that provides ... the functionality "runs on Tivo DVRs". ... source code, which must be distributed under the terms of Sections 1 ... WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. ...
      (Linux-Kernel)
    • Re: Would I be violating the GPL?
      ... > A supplier of a PCI mezzanine digital IO card has provided a linux 2.4 ... > distributing the source code), or the proprietary source code license ... > as currently imposed by the supplier. ... I suspect all kernel modules are probably derivative works but I am not ...
      (Linux-Kernel)
    • Re: starting with 2.7
      ... >> You're effectively arguing that very little should happen. ... This must be considered relative to the size of the source code. ... as the kernel may then benefit from economies of scale. ... >> getting more peer review for patches, ...
      (Linux-Kernel)
    • Re: Closed source apps....
      ... Linux / GPL developers do not necessarily care about 'public image ... The requirements to run closed source applications on the Linux ... kernel and LPGL libraries are not necessarily that onerous. ... Linux is by source code and compiling it on the target machine. ...
      (comp.os.linux.development.apps)
    • Re: VMWare on current kernels
      ... kernel and the source code, is that the source code by default ... or as you suggested use a selfconfigured kernel. ... I get zero problems running VMware on a stock Debian kernel. ... It would be in your best interest to install them. ...
      (Debian-User)