Thanks for the help. I'll review the C extensions that we only use on this
particular server since I think it's the only one that crashes with this error.
RE: rename - we use this command when the server boots but not while it's
running. Do you know if crashes occur when the rename function is
This code produce Segmentation fault
proc x {} {
puts [info level]
catch {
x
}
}
In log :
1
2
3
4
...
48
49
50
51
Segmentation fault
Who can help me ?
Is urgent.
--
Petrica Clement Chiriac
Don't do that! You have an infinite recursion here. You need to include
some condition in the code which will stop the recursive calls to x at
some point (preferably before 50 levels of recursion).
On 1/16/02 12:08 PM, Chiriac Petrica Clement [EMAIL PROTECTED] wrote:
This code produce
My code is an example for real problem.
How can change this value 50 ?
Why produce Segmentation fault ?
Peter M. Jansson wrote:
Don't do that! You have an infinite recursion here. You need to include
some condition in the code which will stop the recursive calls to x at
some point
Your code doesn't do any work -- it's the same as:
proc x {} {
set somevalue 1
while 1 {
puts $somevalue
incr somevalue
}
}
Except that my version won't consume the stack until the process breaks. It
still doesn't do any work! (You get
My OS is RedHat 7.2.
Under RedHat 6.2 work best !
Petrica.
Infinite loops are platform independent. Your code has an infinite loop.
What are you trying to do?
On 1/16/02 12:38 PM, Chiriac Petrica Clement [EMAIL PROTECTED] wrote:
My OS is RedHat 7.2.
Under RedHat 6.2 work best !
I have a template mechanism for generate html static pages.
I can't detect where is Segmentation fault.
Peter M. Jansson wrote:
Infinite loops are platform independent. Your code has an infinite loop.
What are you trying to do?
On 1/16/02 12:38 PM, Chiriac Petrica Clement [EMAIL
Do you think the proc you previously sent is an example of the problem, or
is it just something else that generates a segmentation fault? The code you
previously sent has the error I've mentioned, which will cause a
segmentation fault. If you have a similar piece of code, you need to fix it
in
The only two solutions i see so far is maybe:
proc x {} {
puts [info level]
if { [catch { x }] } {
return
}
}
Or, there is always...
ns_section ns/threads
ns_param stacksize \
1
In 006801c19eb0$3684f380$[EMAIL PROTECTED], on 01/16/02
at 10:07 AM, Daniel P. Stasinski [EMAIL PROTECTED] said:
The only two solutions i see so far is maybe:
proc x {} {
puts [info level]
if { [catch { x }] } {
return
}
}
Or, there is
Jim Wilcoxson wrote:
Thanks for the help. I'll review the C extensions that we only use on this
particular server since I think it's the only one that crashes with this error.
RE: rename - we use this command when the server boots but not while it's
running. Do you know if crashes occur
The AOLserver weekly chat takes place tomorrow, 2002-01-17, and
every Thursday. Common topics include AOLserver, Tcl, SQL, ACS,
and general web-related questions.
The place: AIM chatroom AOLserver on exchange 4
The time: 20:00 UTC
During the summer, that time is
4 PM US/Eastern
3 PM
13 matches
Mail list logo
