[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:	DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:	Welcome to the Digital UNIX Conference
Moderator:	SMURF::DENHAM

Created:	Thu Mar 16 1995
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	10068
Total number of notes:	35879

8587.0. "Can't grow stack !!" by VAXRIO::63222::Manoel () Fri Jan 24 1997 14:16

	Hi, everyone

	There is a  customer trying to create a Thread in a CXX program,
and he received a message that complains about the size of the stack, but
the stack size is 8Mbytes, and it is not supposed to be a problem.
	The complete error message goes below, and the messages in 
portuguese are translated in parenteses.
*************************************************************************
% SML.1.0.15

Handshake message received

Handshake message replied
ID 1010
Vou criar o Data Input Driver (going to create the data input driver)

Vou criar o thread (going to create the thread)
sendsig: can't grow stack, pid 1017, proc SML.1.0.15, sig 11, pc
0x12006c7a0
Segmentation fault (core dumped)
*************************************************************************
	The environment is:
	Digital Unix 2.0
        Cxx Versao 1.3A-0

	The values defined in config file are:

	dfldsiz       138240000
	maxdsiz       1073741824
	dflssiz       8132000
	maxssiz       33554432

	If it is necessary I can post here the Cxx code to be analysed.
	Thanks in advance for any help.
	Regards.
MFAN(MCS/DEC-Rio)

T.R	Title	User	Personal Name	Date	Lines
8587.1	"unlimit" is your friend	PERFOM::HENNING		`Fri Jan 24 1997 15:52`	8
	if running the c shell, say limit to find out whether the config file values apply to the current process, or if it obeying some lesser limit. Then say "unlimit" and say "limit" again. You do realize that Unix 2.0 is, um, rather old?
8587.2	Little more detail.	VAXRIO::63222::Manoel		`Mon Jan 27 1997 11:35`	9
	Hi, Henning The limit command shows 8Mbytes, exactly what is stated in the config file, but the customer feels this is more than enought, he sent me the code, but I know nothing about C programming. Do you have any other idea ? MFAN(MCS/DEC-Rio)
8587.3	Unix v2.0 is from well before my time	PERFOM::HENNING		`Mon Jan 27 1997 11:53`	1
	Sorry my guess didn't help...
8587.4		SMURF::DENHAM	Digital UNIX Kernel	`Mon Jan 27 1997 12:12`	5
	The thread/process is probably stuck in some awful interative SEGV or similar signal. You can provide just as much stack space as possible and the result will eventually be the same. What does the core file show? Stack trace? What kind of application? Etc.
8587.5	limit has no effect on threads...anyway, this is a recursive SEGV.	WTFN::SCALES	Despair is appropriate and inevitable.	`Tue Jan 28 1997 13:40`	9
	Does the application have a handler for SIGSEGV? (Yes, this is almost certainly a recursive SEGV problem.) BTW, limit/unlimit only affects the initial thread's stack (i.e., the initial thread is the one which calls main()). The stacks of explicitly created threads are controlled by the application and are unaffected (in general) by limit. Webb