Processing of tcsh stops due to wait for getting a lock

Solution Verified - Updated -

Issue

  • Processing of tcsh stops due to wait for getting a lock for main_arena of malloc.
  • According to the following backtrace of tcsh core, it seems that tcsh cannot get the lock for main_arena of malloc though it is trying to get the lock in the fork function.
  (gdb) bt
  #0  0x00000038032e027e in __lll_lock_wait_private () from /data/inc/incoming/014-0916-1680/cocore/libc.so.6
  #1  0x0000003803276c45 in _L_lock_57 () at malloc.c:6205
  #2  0x000000380326f4e3 in ptmalloc_lock_all () at arena.c:290
  #3  0x000000380329a5c6 in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/fork.c:92
  #4  0x000000000041e554 in inet_addr () at inet_addr.c:93
  #5  0x0000000000414bd9 in inet_addr () at inet_addr.c:93
   :
  #13 0x000000000040f658 in inet_addr () at inet_addr.c:93
  #14 0x000000000040eb5d in inet_addr () at inet_addr.c:93

Environment

  • Red Hat Enterprise Linux (RHEL) 5
  • tcsh-6.14-17.el5_5.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content