sdb behavior

[Pete Holsberg]

In article <11537 at uwm.edu> adk at csd4.csd.uwm.edu (Andrew D Kailhofer) writes:
=In article <1991Apr25.201206.12430 at mccc.edu> pjh at 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.

It turns out that the error was in the kernel's floating point driver.

=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...

But why does it say "no source file"???  I'm in the directory that
contains core, program and program.c.

Pete
-- 
Prof. Peter J. Holsberg      Mercer County Community College
Voice: 609-586-4800          Engineering Technology, Computers and Math
UUCP:...!princeton!mccc!pjh  1200 Old Trenton Road, Trenton, NJ 08690
Internet: pjh at mccc.edu	     Trenton Computer Festival -- 4/20-21/91