Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!decvax!ucbvax!AMAX.NPAC.SYR.EDU!jerryp From: jerryp@AMAX.NPAC.SYR.EDU (Jerry Peek) Newsgroups: comp.mail.mh Subject: Need help: MH6.5 commands drop core on Multimax (related to sequences?) Message-ID: <8802242037.AA07804@amax.NPAC.SYR.EDU> Date: 24 Feb 88 20:37:55 GMT Sender: usenet@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 74 [I'm sorry if this is the wrong place; maybe this message should have gone to Bug-MH@UCI instead?] We've just started running MH on an Encore Multimax 320 running UMAX 4.2. We have MH 6.5. It compiles fine -- comp and scan work, too -- but many commands (rmm, folders, repl, forw, maybe others?) dump core. I think it has something to do with the .mh_sequences file -- or a function that reads/writes it?? We've seen stuff like this in the file: cur: 182 ^B: 140 pseq: 182 where the ^B is an ASCII 02. If we take the bogus line out, that doesn't fix the problem. One more clue: if the current message has been removed (if cur points to a missing message), the commands don't seem to dump core. There's a demo script below. Before we dig into the code, I thought I'd ask: Has a bug fix been posted for something like this? Or, any clues where we should start looking? Thanks a lot. --Jerry Peek Northeast Parallel Architectures Center; Syracuse, NY jerryp@amax.npac.syr.edu (315)423-1722 --------------------------------------------------------------------------- Script started on Tue Feb 23 15:17:45 1988 $ folder +inbox inbox+ has 118 messages ( 1- 182). $ pwd /u1/npac/jerryp/.Mail/inbox $ cat -v .mh_sequences cur: 189 pseq: 1 $ scan cur scan: no cur message $ forw forw: no cur message $ mark -seq cur last $ scan cur 182+ 02/23 nicky@amax.npac.s Meeting time changed <