Subject: Unaligned access pid=26005 <pine> va=14008a174 pc=1200752f4 ra=1200752e8 type=stq

From: Brad <[email-masked]>
Date: Wed, 5 Oct 1994 16:42:00 +0100 (BST)

This is the message I get when using Pine in a DECterm which is sized
at something other than the default 24 x 80: 

	Unaligned access pid=26005 <pine> va=14008a174 pc=1200752f4
ra=1200752e8 type=stq

	When I go into an index (and this is the only time it occurs), with
the setup different to the default (such as now, it is 48 x 132), this is
what I get, and the longer the index, the more I get; sometimes pages of
these messages (arranged rather messily, not one per line or anything), if I
enter a large index. Does anyone have any idea what may be causing this?
Thanks. 

	--Simon. 

	(Well, at least ^_ works in a DECterm!)

---

From: David L Miller <[email-masked]>
Date: Wed, 5 Oct 1994 10:23:53 -0700

Fixed in Pine 3.91...

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing, JE-20
4545 15th Ave NE, Seattle WA 98105, USA

On Wed, 5 Oct 1994, Brad wrote:

> Date: Wed, 5 OCT 1994 16:42:00 +0100 (BST) 
> From: Brad <[email-masked]>
> Newgroups: comp.mail.pine
> Subject: Unaligned access pid=26005 <pine> va=14008a174 pc=1200752f4 ra=1200752e8 type=stq 
>

---

From: [email-masked] (Raleigh Moody)
Date: 6 Oct 1994 22:41:41 GMT

We recently installed PC-Pine 3.90 for the users on our Novell LAN.  We 
use the LanWorkgroup 4.2 TCP/IP stack.  We are having an intermittent 
problem with Pine suddenly aborting and exiting to DOS, displaying the
message:

   Bug in Pine detected: "Bad msgno in mail_fetchtext"  
   Exiting Pine.

It will most often do this when attempting to save a message to a folder, 
but has also happened when a user simply tries to delete a message, 
forward a message, or even read a message from the inbox list.

I at first thought it might be an incorrect imap version problem, so I 
downloaded imapd-bin.solaris from ftp.cac.washington.edu, then installed 
it on our Sparc5 mail/domain server (yes, I did a "kill -1 <pid>" to 
restart the daemon...I know some of you will ask).

This didn't solve the problem.

The curious thing about this problem is that it surfaces intermittently, 
and happens to different users at different times.  It might work fine 
for a week or so, with the user saving and deleting files at will, with 
no problems at all, then one day start acting up.  So, 90% of the time 
Pine works flawlessly, it's just that 10% that becomes very annoying, 
because it kicks you out without warning.  When this happens, Pine of 
course generates 4 or 5 debug files.

Has anybody experienced a similar problem?  I've followed the messages on 
this group for several weeks without spotting any problems that sound similar.
I've also looked through the the tech-notes, FAQ, and even the August 
mail list archive, and found no hints or reports of similar problems.

Advice, anyone?

-----------------------------------------------------------------------
 Raleigh Moody        Network Specialist      email   [email-masked]
 California Western School of Law             phone   619-525-1406
 San Diego, CA                                fax     619-685-2916
-----------------------------------------------------------------------