jreuter (05/14/82)
Adb doesn't seem to be able to handle core files or breakpointing on our 2.8bsd systems. Core files always generated the "bad core magic number" diagnostic, which I figured was just a problem with adb's idea of the system process info. Attempting to recompile it revealed that the constant SIGTRC was undefined in runpcs.c. There is a SIGTRAP and also a SETTRC, but neither of these see to help. Compiled with either of these, it no longer complains about the bad core magic number, but stack tracebacks don't work. Breakpointing doesn't work either--breakpoints cause breaks, but the pc shows a ridiculous value (0170???). It is no fun not being able to analyze core dumps!! Has anybody got information that would help? Jim Reuter