obviously, i'll need the actual vmlinux kernel file (which i mightYes, you need vmlinux if you want the addresses to be resolved back to the related original symbols. But see below..
not have if i've simply sat down at someone else's system.)
This is where DEBUG_INFO needed. Without it, vmlinux is pretty useless because it isn't equipped with symbol table. IIRC, enabling DEBUG_INFO will compile vmlinux with -g (or maybe -ggdb).also, must that kernel have been configured with DEBUG_INFO? i realize that selecting that config option gives me access to kernel variable names, but do i actually need that info? would i be able to use gdb to dump what i want by address if i have a System.map file that tells me where "jiffies" lives in kernel space instead?
this config item controls the presence of that --> CONFIG_PROC_KCOREand i'm aware that, even as root, the contents of /proc/kcore might not be available. under what circumstances is that true?
in short, what is the absolute *minimum* i would need on a system toI think you can conclude it by your own after reading my above short explanation.
be able to dump the contents of some kernel values? thanks.
-- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ