Re: [Crash-utility] crash version 4.0-4.4 is available

Bernhard Walle wrote: And this is why I coerced Cliff into the support of this venture... ;-) Anyway, Cliff and I went back-and-forth through several patch submissions, and one of the things that I did insist upon was that the Kerntypes-specific code be totally segregated from the "traditional" code. (You can see a number of "LKCD_KERNTYPES()" checks that do just that.) But that's why the vmlinux file usage still should work "flawlessly"... My guess is that Cliff was using an older kernel that was able to either use the "if" block of this if-else statement, or that either next_online_node() or next_online_pgdat() worked OK: * This order may have to change based upon architecture... */ if (symbol_exists("pgdat_list") && (VALID_MEMBER(pglist_data_node_next) || VALID_MEMBER(pglist_data_pgdat_next))) { get_symbol_data("pgdat_list", sizeof(void *), &pgdat); vt->flags &= ~NODES_ONLINE; } else if (vt->flags & NODES_ONLINE) { if ((node = next_online_node(0)) < 0) { error(WARNING, "cannot determine first node from node_online_map\n\n"); return; } if (!(pgdat = next_online_pgdat(node))) { error(WARNING, "cannot determine pgdat list for this kernel/architecture\n\n"); return; } } I guess I'd work back from there -- figure out what it does "right" when you use the vmlinux, and determine why it doesn't take that path when using the kerntypes file. But as to why the "p jiffies" failed, I'm sure I don't understand why that doesn't work? Cliff -- correct me if I'm wrong -- simple gdb commands against a kerntypes file should work OK, correct? Dave