Bug 1473 - pdksh + glibc2.1 = coredump on startup (trap.c ~line 34)
pdksh + glibc2.1 = coredump on startup (trap.c ~line 34)
Status: CLOSED CURRENTRELEASE
Product: Red Hat Raw Hide
Classification: Retired
Component: pdksh (Show other bugs)
1.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
:
: 1408 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-03-10 14:51 EST by jmegq
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-03-17 15:48:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description jmegq 1999-03-10 14:51:19 EST
With glibc 2.1, pdksh coredumps on startup.
GDB says this occurs in trap.c around line 34, where
it attempts to fill in a list of signal descriptions
using sys_siglist.

Workaround: after running configure, comment out
the HAS_SYS_SIGLIST line in config.h, then compile
as usual.  sys_siglist says it's "only for compatability"
in 2.1, but it appears not to be so compatable...
Comment 1 Jeff Johnson 1999-03-17 15:43:59 EST
*** Bug 1408 has been marked as a duplicate of this bug. ***

Ksh segfaults on any script I try to run. For example:

-----------------------------------------
#!/bin/ksh

echo foo
-----------------------------------------

------- Additional Comments From abel@bfr.co.il  03/16/99 10:53 -------
Actually it is enough to invoke 'ksh' from command line to see it
crashing. It is still relevant in 5.8.6 (pdksh-5.2.12-7)
Comment 2 Jeff Johnson 1999-03-17 15:48:59 EST
Fixed in pdksh-5.3.12-2 (by checking that sys_siglist[i] != NULL).
Thanks.

Note You need to log in before you can comment on or make changes to this bug.