Subject: Any known problems with pico and AIX 3.2?

From: [email-masked] (Alessandro Miotto)
Date: Tue, 4 Jul 1995 15:59:34 GMT

I have been reported a couple of problems by pine users on AIX 3.2
(we are using several different architectures at this site and this 
looks specific to the AIX version).
I have no core or pine-debug information yet so I would like to understand
whether similar behaviours are already known before investigating further.

Both problems seem to be related with pico, as they happened when composing
a message:
- A pine with no terminal attached (!) was found consuming all available CPU.
  The stack trace was inside pico.
- In another session pico kept pasting the same buffer over and over until
  it was killed by hand. The text was saved into the postponed messages
  folder, and when restarted pine asked whether the user wanted to resume
  composition. After typing "yes" the program crashed.

	Alessandro

---------------------------------------------------------------------------
 Alessandro Miotto - CN/DCI/UES      | Tel:    +41 22 767 9576
 CERN - European Laboratory          | Fax:    +41 22 767 7155
 for Particle Physics                | E-mail: [email-masked]
 CH-1211 Geneve 23                   |
--
---------------------------------------------------------------------------
 Alessandro Miotto - CN/DCI/UES      | Tel:    +41 22 767 9576
 CERN - European Laboratory          | Fax:    +41 22 767 7155
 for Particle Physics                | E-mail: [email-masked]

---

From: [email-masked] (Kurt)
Date: Wed, 05 Jul 1995 15:48:04 GMT

>	Alessandro

I have had pine crash under AIX 3.2.0 when choosing C to compose a new
message, and also when choosing C to continue composing an interrupted
message.  When it crashes, it squirts reversed question marks and
other bizzarre characters onto the terminal, then hangs.  I have to
kill pine from another terminal...

Kurt Risser
Snider Bolt, Louisville, KY USA   502 968-2250

---

From: Joshua Hosseinoff <[email-masked]>
Date: Sun, 9 Jul 1995 15:08:44 -0400

This is the typical linking with curses problem on AIX, just link it with 
termcap instead of curses and find yourself a decent termcap file and 
you're all set.