Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!mcvax!swivax!jan
From: jan@swivax.UUCP (Jan Wielemaker)
Newsgroups: comp.unix.questions
Subject: debugging incremental loaded executables
Message-ID: <427@swivax.UUCP>
Date: Tue, 13-Oct-87 10:30:30 EDT
Article-I.D.: swivax.427
Posted: Tue Oct 13 10:30:30 1987
Date-Received: Thu, 15-Oct-87 20:02:05 EDT
Reply-To: jan@swivax.UUCP (Jan Wielemaker)
Organization: SWI, UvA, Amsterdam
Lines: 23

We've got a system called PCE-Prolog, consisting of an  object  oriented
interface/data   management   system,   connected  to  Prolog.   We  can
dynamically add new classes to  the  object  oriented  part  by  writing
C-code,  compiling  this  into object files and then load these into the
running PCE process.   This  is  done  by  calling  'ld'  to  create  an
incremental  executable  with  some base address, loading the executable
and resolving the  entry  points.   This  feature  is  mainly  used  for
prototyping classes.

Problem is that on an error 'adb' doesn't understand the  core  file  as
the  symbol  table  is  incomplete.   The  symbol  table  of the created
executable is complete, but as the text of this file is  incomplete  adb
still  refuses to produce a stack trace.  (The system is running on SUN,
under SunUnix 3.2).

My questions are:
	1) Does anyone know a way to have 'adb' produce a stack trace
	   for me?
	2) (Even better) does anyone have a routine, which I can insert
	   as signal handler, which prints the stack for me, given some
	   symbol table.

	Thanks --- Jan