[13266] in Athena Bugs

home help back first fref pref prev next nref lref last post

decmips 7.7G: xess

daemon@ATHENA.MIT.EDU (alexp@MIT.EDU)
Wed Mar 1 19:56:16 1995

From: alexp@MIT.EDU
Date: Wed, 1 Mar 1995 19:56:05 -0500
To: rdhamlin@MIT.EDU, bugs@MIT.EDU
Cc: alexp@MIT.EDU


Hello,

I'm looking at your TSV import bug report with Xess. I'm really sorry this
took so long- it got lost in the input queue. I don't know if you still
have it, but it would be very helpful if you could send me the file (or a
file) that triggers the problem so I can reproduce it. You could mail it
or put it in your Public directory where I could pick it up.

                                      Alex Prengel, Jr.
                                      Academic Computing Services
                                      Software Acquisition Coordinator

>From rdhamlin@MIT.EDU Wed Dec  7 16:32:24 1994
>Received: by gregor.MIT.EDU (5.57/4.7) id AA20916; Wed, 7 Dec 94 16:32:22 -050>0
>Received: from M1-142-22.MIT.EDU by MIT.EDU with SMTP
>	id AA12330; Wed, 7 Dec 94 16:32:20 EST
>From: rdhamlin@MIT.EDU
>Received: by m1-142-22.MIT.EDU (5.57/4.7) id AA02111; Wed, 7 Dec 94 16:32:19 ->0500
>Message-Id: <9412072132.AA02111@m1-142-22.MIT.EDU>
>To: bugs@MIT.EDU
>Subject: decmips 7.7G: xess
>Date: Wed, 07 Dec 1994 16:32:18 EST
>
>System name:		m1-142-22
>Type and version:	KN02ca 7.7G
>Display type:		PMAG-DV 
>
>What were you trying to do?
>	Importing a TSV file.  I clicked on the file that I wanted, and about
>	the time I hit ok, Garbage characters started spewing into the work
>	space.
>
>What's wrong:
>
>	I clicked on the file that I wanted, and about
>	the time I hit "ok", Garbage characters started spewing into the work
>	space.  I am not sure on the order, it was too close to tell.
>	It certainly did not have time to retrieve the file over afs though.
>	Then it died and I got:
>
> pid 1876 (xess3) was killed on an unaligned access, at pc 0x646f6d2e 
>
>What should have happened:
>
>	It should have just loaded the file ofcourse.  It did this
>when I loaded up xess again.  This is a different error, but it does not
>parse properly into fields if there are too many significant digits:
>E.g.
>
>3.25809653802148	2.56494935746154	1960.73	2.9391619220656	NA	5.17110879980699	>0.333333333333333	NA	DS	NA	2.59140401898289	NA	NA	NA	-2.56494935746154
>
>Please describe any relevant documentation references:
>
>

home help back first fref pref prev next nref lref last post