Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!umn-d-ub!umn-cs!randy From: randy@umn-cs.UUCP Newsgroups: comp.lang.c,comp.unix.questions Subject: Re: C Programs and sdb Message-ID: <3059@umn-cs.cs.umn.edu> Date: Fri, 4-Dec-87 20:16:02 EST Article-I.D.: umn-cs.3059 Posted: Fri Dec 4 20:16:02 1987 Date-Received: Tue, 8-Dec-87 07:09:49 EST References: <161@mccc.UUCP> <2143@dasys1.UUCP> Reply-To: randy@umn-cs.UUCP (Randy Orrison) Organization: UofM Math Department Lines: 26 Keywords: debug C Xref: utgpu comp.lang.c:5415 comp.unix.questions:4652 In article <2143@dasys1.UUCP> manes@dasys1.UUCP (Steve Manes) writes: >In article <161@mccc.UUCP> pjh@mccc.UUCP (Peter J. Holsberg) writes: [about a program that dumps core in a non-existant file strncpy.c] >> >>What could be wrong??? > >Don't forget that C libraries also reference themselves and that a core >dump on something like 'strncpy' or 'strcmp' may not be one that you put in >your source file but called from something like printf(). I haven't yet seen anyone mention the obvious solution: There's a call to the library strncpy routine in his program, and he's passing it a NULL (or other invalid pointer). Here's a question: why don't they put absolute path names in library modules? It wouldn't be any worse than the current situation, and in many cases (sites with source liscense, who use it) it would be reall handy. -randy -- Randy Orrison, University of Minnesota School of Mathematics | May the smiley UUCP: {ihnp4, seismo!rutgers, sun}!umn-cs!randy | O__\, ARPA: randy@ux.acss.umn.edu BITNET: randy@umnacca | O /' Disclaimer: No one is silly enough to pay me to do this. | be with you!