The version used to reproduce the problem on RHEL3 was tcsh-6.12-11.EL3, on i386.

+++ This bug was initially created as a clone of Bug #188279 +++

We got the segmentation fault of tcsh when executing their csh
script.  However, the csh script is not related to segmentation fault.
Using RHEL4 IA64.  Also, the architecture is not related. 

Version-Release number of selected component (if applicable):
tcsh-6.13-9

How reproducible:
Sometimes

Steps to Reproduce:
Executing a csh script

Actual results:
core dump

Expected results:
no core dump

Additional info:

The customer is using tcsh-6.13-9.ia64. The following is backtrace of
dump.
__stack_pointer is 0x0, and snum in palarm() is wrong, too.

(gdb) bt
#0  0x20000000000f6fb0 in __longjmp () at ../string/bits/string2.h:1000
        __thread_self = (struct pthread *) 0x200000000030cac0
        __stack_pointer = 0x0
        _nl_msg_cat_cntr = 4
#1  0x20000000000f6e60 in __libc_siglongjmp (env=0x6000000000039520,
val=1)
    at ../sysdeps/generic/longjmp.c:39
No locals.
#2  0x400000000009a860 in palarm (snum=67552) at tc.func.c:2096
No locals.
#3  <signal handler called>
No symbol table info available.
#4  0x6000000000628ea0 in ?? ()
No symbol table info available.