Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1473

Summary:	pdksh + glibc2.1 = coredump on startup (trap.c ~line 34)
Product:	[Retired] Red Hat Raw Hide	Reporter:	jmegq
Component:	pdksh	Assignee:	Trond Eivind Glomsrxd <teg>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	1.0	CC:	abel
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-03-17 20:48:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description jmegq 1999-03-10 19:51:19 UTC

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 20:43:59 UTC

*** 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.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 20:48:59 UTC

Fixed in pdksh-5.3.12-2 (by checking that sys_siglist[i] != NULL).
Thanks.