As I do all our stuff under VM I use the methods described in the 390Debugging doc. referred to earlier. This involves using the TRACE command to trace paths, events, calls of interest. For example, #CP TR SVC RUN CMD D G2 3 4 5 6 trace all syscall events and display the parameter registers. The doc. shows you how to trace the kernel branches and post process it against the system.map to obtain an annotated trace.
-----Original Message----- Just to clarify things ... I am not looking for 390 specific information. I am looking for tips/suggestions/references/ideas on how to perform kernel debugging on an s390 install. I have worked on i386 and ppc but the s390 is still elusive. Other than sprinkling printk stmts (my current practice) ... or causing a kernel panic to get a back trace (guilty as charged) ... what are folks doing? kdb, ltt, dprobes ... ?
