Bug 12174 - bash terminate with corefile if pid > 32000
Summary: bash terminate with corefile if pid > 32000
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Andrey A. Chernov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 1999-06-12 20:40 UTC by dinoex.sub.org!dirk.meyer
Modified: 1999-12-29 08:48 UTC (History)
0 users

See Also:

Attachments
file.diff (666 bytes, patch)
1999-06-12 20:40 UTC, dinoex.sub.org!dirk.meyer 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dinoex.sub.org!dirk.meyer 1999-06-12 20:40:01 UTC 
	in comand completition bash terminates:
/kernel: pid 2111 (bash), uid 1000: exited on signal 11 (core dumped)
/kernel: pid 81266 (bash), uid 1000: exited on signal 11 (core dumped)
/kernel: pid 81276 (bash), uid 1000: exited on signal 11 (core dumped)
/kernel: pid 81301 (bash), uid 1000: exited on signal 11 (core dumped)
/kernel: pid 404 (bash), uid 0: exited on signal 11 (core dumped)
/kernel: pid 81322 (bash), uid 0: exited on signal 11 (core dumped)
/kernel: pid 1272 (bash), uid 1000: exited on signal 11
/kernel: pid 81494 (bash), uid 0: exited on signal 11 (core dumped)

Fix: this patch seem to fix the problem
How-To-Repeat: 
	the new pid of the system has reached a value > 32736.
	The shell itsel could still have an old pid in range.
	using <TAB> key to complete a path on the command line,
	pressing <TAB> twice to get a list that would create a
	question "Display all xxx possibilities? (y or n)"
Comment 1 jseger freebsd_committer freebsd_triage 1999-06-13 16:10:36 UTC 
Responsible Changed
From-To: freebsd-ports->ache

Over to MAINTAINER.
Comment 2 Steve Price freebsd_committer freebsd_triage 1999-12-29 08:46:38 UTC 
State Changed
From-To: open->closed

Committed, thanks!