thakur@ZERKALO.HARVARD.EDU ("Manavendra K. Thakur") (10/29/90)
Hi all, Several of our users have reported a very annoying problem with xmh. Apparently, xmh likes to add extra numbers in front of the message ID numbers every now and then. When the user tries to click on that message (to read it, etc), either xmh crashes or it displays the wrong message. One reported fix to this problem was to apply a patch (originally written by someone whose name I've forgotten; the patch was distributed to xpert by Donna Converse of the X Consortium) to mit/clients/xmh/tocutil.c. The patch rewrites a for loop to count down rather than up. This work arounds a bug in gcc 1.37.1. However, applying this patch did not solve the problem for us. To confirm this, I compiled xmh with Sun's C compiler (on a Sun 3 running SunOS 4.0.3), and still the problem persisted. So it does not seem like a gcc vs cc issue. Before I dive into xmh code to track this down futher, has anyone else seen this problem? If so, how did you fix it or deal with it? For a better picture of what I'm talking about, here's a report from one of our users [subject lines of the messages have been deleted to protect the user's privacy]: ------- Forwarded Message Nope, this didn't work either. Here's my messages window as displayed by [the Sun CC compiled xmh]: 18+ 10/24 thakur@zerkalo 21 10/25 igioia@astbo1.dec 2 22 10/25 paul@oxmyx 3 23 10/25*belinda@cfa222 4 24 10/25*belinda@cfa222 5 25 10/25*belinda@cfa222 6 26 10/26*john@cfa267 I can display messages 18 and 21 OK but if I try to display message 22, I get message 2, 23, 4, etc. Sometimes (I think when the numbers on the left cycle through, i.e. more than 10 of them), xmh dies when I try to display any of them. ------- End of Forwarded Message Any ideas on this one? Suggestions, hints, even RTFM would be greatly appreciated. Manavendra K. Thakur Internet: thakur@zerkalo.harvard.edu System Manager, High Energy Division BITNET: thakur@cfa.BITNET Harvard-Smithsonian Center for DECNET: CFA::thakur Astrophysics UUCP: ...!uunet!mit-eddie!thakur
hmp@frc2.frc.ri.cmu.edu (Henning Pangels) (10/29/90)
Same problem exists here, but we haven't tried the patch posted earlier. In the meantime, I should mention that a workaround is to rescan or sort the message folder, that gets seems to bring the message numbers back in line. -Henning -- Henning Pangels Research Programmer Field Robotics Center ARPAnet/Internet: hmp@frc2.frc.ri.cmu.edu Robotics Institute (412) 268-7088 Carnegie-Mellon University
converse@EXPO.LCS.MIT.EDU (10/29/90)
> Apparently, xmh likes to add extra numbers in front of the message ID > numbers every now and then. When the user tries to click on that > message (to read it, etc), either xmh crashes or it displays the wrong > message. > > One reported fix to this problem was to apply a patch to > mit/clients/xmh/tocutil.c. The patch rewrites a for loop to count > down rather than up. This work arounds a bug in gcc 1.37.1. > > However, applying this patch did not solve the problem for us. To > confirm this, I compiled xmh with Sun's C compiler (on a Sun 3 running > SunOS 4.0.3), and still the problem persisted. So it does not seem > like a gcc vs cc issue. After recompiling xmh with cc, every xmh user should regenerate the message listing in each affected folder by selecting Rescan Folder from the Table of Contents menu. If it still happens after that, I'll eat my hat.