Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!think!ames!sri-spam!rutgers!iuvax!pur-ee!uiucdcs!snail!carroll From: carroll@snail.CS.UIUC.EDU Newsgroups: comp.lang.c Subject: Re: C Programs and sdb Message-ID: <10700007@snail> Date: Thu, 3-Dec-87 22:28:00 EST Article-I.D.: snail.10700007 Posted: Thu Dec 3 22:28:00 1987 Date-Received: Wed, 9-Dec-87 06:04:51 EST References: <161@mccc.UUCP> Lines: 8 Nf-ID: #R:mccc.UUCP:161:snail:10700007:000:509 Nf-From: snail.CS.UIUC.EDU!carroll Dec 3 21:28:00 1987 I means that the library function "strncmp" had a core dump, and sdb is looking for source to it. Obviously, there isn't any. What you should do is use the "t" command to trace back on the stack, and see what values you passed strncmp. It doesn't do any checking about the pointer values it gets (because that would be a real nightmare to implement, if not outright impossible). If you pass strncmp a bogus pointer, it will go ahead and try to use it, and then core dump, giving the effect you seem to have.