Same problem, make_System_map has to run commands and open files, if
only to read /proc/ksyms and get the nm data for the modules. If you
cannot issue cat or nm commands yourself, then klogd is going to have
the same problem.
However all that is required to diagnose an oops after the machine has
been rebooted is the data in /proc/ksyms at the time of the oops.
Remember that make_System_map does not require the real /proc/ksyms, it
can be a copy. ksyms is the only data that changes from run to run,
System.map and modules are only changed by kernel recompiles. So what
you really need is a way of capturing the current ksyms to a file when
an oops occurs.
That could be a simple extension to klogd, when an oops is detected,
copy /proc/ksyms to a file and run a specified program such as
make_System_map. If my approach to extending the map is accepted, I'll
add that option to klogd later.