bhaskar@tc.fluke.COM (K.S. Bhaskar) (12/25/87)
I ran into a couple of bugs (described below) in 3.51 software for my 3B1
recently. Calling the hotline was a waste of time -- the person did not
understand the problem, kept trying to tell me that I was doing something
wrong, refused to accept that I might know what I was doing, and declined to
file a bug report. He did finally agree to looking at a floppy disk if I
mailed it to him with a written description of the problem. I suppose a
warranty is worth only as much as the commitment to stand behind it...
The following tbl source is botched, both when processed for the screen (tbl |
nroff | col -b) and for a printer (in my case, for an epson, by tbl | nroff
-Tfx-12 | col -xfp | fx). In the first case, the box is drawn through the text
in the second row, second column. On the printer, there are multiple bugs:
- if the first row, second column extends over more than one line, the second
line is indented and bolded
- the second row second column is indented and bolded
- the box is still drawn round the second row, second column
- if there is additional text following the table, it too is bolded
The bug is probably in col, but that is irrelevant, since it is the interaction
of all 3 programs that produce the output. There appears to be no work-around.
When I called the hotline, the person answering the phone tried to tell me that
tbl had no .T& construct! (Btw, you can write the example without the .T&; it
doesn't make any difference to the result.)
.TS
box;
l | l.
T{
First row, first column; no bolding
T} T{
\fBFirst row, second column; bolded\fR
T}
.T&
^t | l.
T{
Second row, second column; second row, first column is formatted ^t
T}
.TE
The following causes ksh to die and leave a core dump. Create a directory with
the files: sof.optics.1.n, sof.optics.n, sof.optics.t, sof.optics.v1,
sof.optics.v2, sof.optics.v3, sof.optics.v4, sof.optics.v5, sof.optics.v6,
sof.optics.v7, and sof.optics.v8 (empty files will do). "cd" to it and type
"ls s<ESC>*" to expand the filenames in-line. Your shell will disappear and
leave a core file in your directory. When I called the hotline, the person
did not understand ksh's immediate filename expansion, and kept insisting that
I should say "ls s*<RETURN>". He was also hung up on exactly what program was
I trying to invoke with what flags.ins_anmy@jhunix.UUCP (Norman M Yarvin) (12/27/87)
In article <2556@fluke.COM> bhaskar@tc.fluke.COM (K.S. Bhaskar) writes: >I ran into a couple of bugs (described below) in 3.51 software for my 3B1 >recently. > [description of tbl bug deleted] > >The following causes ksh to die and leave a core dump. Create a directory with >the files: sof.optics.1.n, sof.optics.n, sof.optics.t, sof.optics.v1, >sof.optics.v2, sof.optics.v3, sof.optics.v4, sof.optics.v5, sof.optics.v6, >sof.optics.v7, and sof.optics.v8 (empty files will do). "cd" to it and type >"ls s<ESC>*" to expand the filenames in-line. It is much easier to blow up ksh in the following manner: press your hand flat down on the keyboard, and perform CPR (i.e. make lots of keypresses.) After a few applications of the hand, ksh will crash. It appears that ksh cannot handle more about than two screen-widths of text before going into the twilight zone. Norman Yarvin (seismo!umcp-cs | ihnp4!whuxcc | allegra!hopkins) !jhunix!ins_anmy
ford@crash.cts.com (Michael Ditto) (12/28/87)
In article <5836@jhunix.UUCP> ins_anmy@jhunix.UUCP (Norman Yarvin) writes: >In article <2556@fluke.COM> bhaskar@tc.fluke.COM (K.S. Bhaskar) writes: >>The following causes ksh to die and leave a core dump. >> [ ... example of ksh bug ... ] >It is much easier to blow up ksh in the following manner: press your hand >flat down on the keyboard, and perform CPR (i.e. make lots of keypresses.) > [ ... ] It even easier to just hold down a repeating key. When the line contains about 100 characters, ksh will dump core. Note that this bug only occurs in Emacs editing mode, as far as I know. I reported this bug to the AT&T Hotline several months ago and they sent me a disk with a fixed ksh on it. I'm sure they'll send it to anyone who asks, if they remember fixing it. -- Mike Ditto -=] Ford [=- P.O. Box 1721 ford%kenobi@crash.CTS.COM Bonita, CA 92002 ford@crash.CTS.COM