adb bug?

Article View: net.bugs.2bsd

Article #58

#58

From: utzoodecvaxharpoeaglemhuxtcbosgc...
Date: Fri, 14 May 1982 14:51

13 lines
1042 bytes

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

Technical Details

Message-ID: <bnews.cincy.1112>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers

Complete Article Headers

From: utzoo!decvax!harpo!eagle!mhuxt!cbosg!cincy!jreuter
Newsgroups: net.bugs.2bsd
Title: adb bug?
Article-I.D.: cincy.1112
Posted: Fri May 14 14:51:14 1982
Received: Sat May 15 04:15:34 1982
Subject: adb bug?
Date: Fri, 14 May 1982 14:51:14 +0000
Message-ID: <bnews.cincy.1112>