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.wizards
Subject: debugging incremental loaded executables (any real wizard?)
Message-ID: <442@swivax.UUCP>
Date: Tue, 27-Oct-87 07:09:15 EST
Article-I.D.: swivax.442
Posted: Tue Oct 27 07:09:15 1987
Date-Received: Fri, 30-Oct-87 00:08:12 EST
Reply-To: jan@swivax.UUCP (Jan Wielemaker)
Organization: SWI, UvA, Amsterdam
Lines: 24

Some weeks ago I posted a message on unix.questions, but it seems no one
there could solve the problem (some wrote me they would like to know  as
well).  here is the PROBLEM:

We use a large package of software (executable ca.  1Mb), which consists
of an object oriented interface to SunView  and  a  Prolog  engine.   To
extend   the   object  oriented  part  with  very  specific  classes  we
dynamically load C object files into the system (using ld -A  -T  etc.).
This  works  fine,  exept for one problem: ADB doesn't make sense out of
the core dumps.  This is understandable  as  the  symbol  table  of  the
original  executable  isn't  complete.  Unfortunately adb refuses to use
the symbol table of the incremental executable as well (why?).

My QUESTIONS:

	1) Is there someone there who knows how to get adb producing a
	   stack trace for me?
	2) (Even better) Is there someone who has a routine which I can
	   insert as a signal handler, which dumps the stack and exits
	   without producing about 3 Mb of core.

	Thanks --- Jan Wielemaker (jan@swivax.UUCP, or ...mcvax!swivax!jan)

P.s. We are using SUN's under SunUnix 3.2