Xref: utzoo comp.sys.att:12206 comp.unix.programmer:1695
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uwm.edu!csd4.csd.uwm.edu!adk
From: adk@csd4.csd.uwm.edu (Andrew D Kailhofer)
Newsgroups: comp.sys.att,comp.unix.programmer
Subject: Re: sdb behavior
Summary: It all depends on "who" dumped the core...
Keywords: sdb core dumps sources
Message-ID: <11537@uwm.edu>
Date: 29 Apr 91 17:11:12 GMT
Article-I.D.: uwm.11537
References: <1991Apr25.201206.12430@mccc.edu>
Sender: news@uwm.edu
Followup-To: comp.sys.att
Organization: University of Wisconsin - Milwaukee
Lines: 19

In article <1991Apr25.201206.12430@mccc.edu> pjh@mccc.edu (Peter J. Holsberg) writes:
>I have a program that dumps core but when I invoke sdb with the name of
>the executable, sdb says "no source file."  The command line I used is
>simply "sdb program".  Program was built from "cc -g -o program program.c".

Being an habitual System V person, I've seen this sort of thing
before.  There are several ways that this can be caused, the best two
contenders being (1) you aren't in the directory containing the source
of your code, or (2) [and I believe this is your problem] the error
actually occurred someplace inside a library call or some such like
that.  You might want to try doing a 't' and seeing what the stack
trace says, if it says anything.  Sdb isn't really very smart, and
gets pretty confrused if pointers get screwed up, which is also one of
the things that causes library calls to blow up...

--------------------
Andy Kailhofer			Ameritech Services, Inc.
a907932@nast0.wi.ameritech.com  740 N. Broadway, Rm 430
414/678-7793			Milwaukee, WI  53202