Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!uwvax!uwmacc!uwspan!root From: root@uwspan.UUCP (John Plocher) Newsgroups: comp.unix.xenix Subject: smail 2.5 under uPort/286 Message-ID: <186@uwspan.UUCP> Date: Sun, 15-Nov-87 21:15:59 EST Article-I.D.: uwspan.186 Posted: Sun Nov 15 21:15:59 1987 Date-Received: Tue, 17-Nov-87 05:51:26 EST References: <427@ncc.UUCP> Sender: root@uwspan.UUCP Reply-To: root@uwspan.UUCP (John Plocher) Followup-To: comp.unix.xenix Distribution: comp Organization: UW-Madison Spanish Dept Lines: 33 +---- lyndon@ncc.UUCP (Lyndon Nerenberg) writes in <427@ncc.UUCP> ---- | I've compiled smail 2.5 without any trouble, however the silly | thing core dumps with a memory fault. THEN I discover there's | no adb(1) on the system! +---- I'm using smail2.5 (installed on Sept 30, 19:28) and according to the file timestamps, I didn't modify anything. I don't know what your problem is, but sdb works quite well for finding bugs. Compile smail with CFLAGS = -O -Ml and DO NOT USE -lmalloc -lmalloc has bugs; if you used it then that is your problem. To find out where the program bombs, add the -g flag to CFLAGS, make, and run smail. When it dumps type in % sdb smail *t *q % This will print out a procedure name trace with line numbers. sdb(1) is (in some ways) better than adb, but gawd, I miss adb too! -John -- Email to unix-at-request@uwspan with questions about the newsgroup unix-at, otherwise mail to unix-at@uwspan with a Subject containing one of: 386 286 Bug Source Merge or "Send Buglist" (Bangpath: rutgers!uwvax!uwspan!unix-at & rutgers!uwvax!uwspan!unix-at-request)