Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Aug 2002 11:14:14 +0200
From:      Martin Kraemer <Martin.Kraemer@Fujitsu-Siemens.com>
To:        FreeBSD-stable@freebsd.org, tcsh@mx.gw.com
Subject:   Strange bug: tcsh stops reading .tcshrc after 4kB
Message-ID:  <20020829111414.A54912@deejai2.mch.fsc.net>

next in thread | raw e-mail | index | archive | help
On FreeBSD (I assume this is related to the bug) I "often"
experience a very strange bug which was not there in the past.
It manifests by tcsh not finishing reading all of .tcshrc (or/and
.login).
Especially strange is the fact that it does not always happen, but only
when tcsh is started from the x11 window manager directly, not (or at least,
not always) when started from another tcsh. The exact trigger is still
unknown to me.

To visualize what happens, I added this in my .tcshrc around the magic
4kB boundary:
  ...
  set autolist = ambiguous
  if ( $?prompt ) echo -n '117 '
  set addsuffix           # (set by dflt)
  if ( $?prompt ) echo -n '119 '
  set autocorrect
  if ( $?prompt ) echo -n '121 '
  set autoexpand
  if ( $?prompt ) echo -n '123 '
  if ( ! $?DISPLAY ) set autologout = 60
  if ( $?prompt ) echo -n '125 '
  set backslash_quote
  if ( $?prompt ) echo -n '127 '
  set complete = enhance  #
  if ( $?prompt ) echo -n '129 '
  set correct = cmd       # all | complete | cmd
  if ( $?prompt ) echo -n '131 '
  set echo_style = both   # bsd | sysv | both | none
  if ( $?prompt ) echo '133'
  unset dextract          # pushd +n extracts instead of rotating?
  ...
or as a hex dump around 0x1000:
00000fc0  74 20 29 20 65 63 68 6f  20 2d 6e 20 27 31 31 37  |t ) echo -n '117|
00000fd0  20 27 0a 20 20 20 20 73  65 74 20 61 64 64 73 75  | '.    set addsu|
00000fe0  66 66 69 78 20 20 20 20  20 20 20 20 20 20 20 23  |ffix           #|
00000ff0  20 28 73 65 74 20 62 79  20 64 66 6c 74 29 0a 69  | (set by dflt).i|
00001000  66 20 28 20 24 3f 70 72  6f 6d 70 74 20 29 20 65  |f ( $?prompt ) e|
00001010  63 68 6f 20 2d 6e 20 27  31 31 39 20 27 0a 20 20  |cho -n '119 '.  |

Now I can see where tcsh stops reading.
When starting tcsh from fvwm, I see:
117 
but when doing an "exec tcsh -l" in this newly opened tcsh window,
I see all instrumented numbers:
117 119 121 123 125 127 129 131 133

I already tried to instrument the sources to see WHY tcsh would stop
reading in the middle of a file, but I find no clues.

So my question is: has anybody else observed the same strange problem?

This happens both in 6.12.00 and also in 6.11.04 for me, at least (and
I had been using 6.11.04 for a long time without noticing this problem),
so I assume it is a FreeBSD specific problem.

   Martin
-- 
<Martin.Kraemer@Fujitsu-Siemens.com>         |     Fujitsu Siemens
Fon: +49-89-636-46021, FAX: +49-89-636-47655 | 81730  Munich,  Germany

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020829111414.A54912>