Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

./configure locks system up #2929

Closed
vicuna opened this issue Aug 26, 2001 · 2 comments
Closed

./configure locks system up #2929

vicuna opened this issue Aug 26, 2001 · 2 comments
Labels
bug

Comments

@vicuna
Copy link

vicuna commented Aug 26, 2001

Original bug ID: 495
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)

Bug description

Full_Name: Gerd Stolpmann
Version: latest CVS version
OS: Linux-2.2.18
Submission from: drms-3e364bb9.pool.mediaways.net (62.54.75.185)

Hello,

I've just update my CVS workspace and tried to compile OCaml. However, there
is a serious problem in the configure script. While checking whether stack
overflows can be detected, the system locks up for a while, and after some
minutes
the (Linux-2.2) kernel decides to kill processes to keep the system running.
Of course, this is mainly a well-known flaw in the Linux virtual memory manager,
but I
think a configure script should not run into such a problem.

After setting a ulimit for the stack size (ulimit -s 10000), everything
worked fine.

Gerd
@vicuna
Copy link
Author

vicuna commented Aug 27, 2001

Comment author: administrator

Gerd,

I've just update my CVS workspace and tried to compile
OCaml. However, there is a serious problem in the configure
script. While checking whether stack overflows can be detected, the
system locks up for a while, and after some minutes the (Linux-2.2)
kernel decides to kill processes to keep the system running.

I guess this didn't happen to me because of a lower stack limit than yours.

Of course, this is mainly a well-known flaw in the Linux virtual
memory manager, but I think a configure script should not run into
such a problem.

Agreed.

After setting a ulimit for the stack size (ulimit -s 10000), everything
worked fine.

I'll change the test code so that it puts a low limit on the stack
before attempting to overflow it :-)

Best regards,

  • Xavier Leroy

@vicuna
Copy link
Author

vicuna commented Aug 28, 2001

Comment author: administrator

Fixed 2001-08-28 by XL.

@vicuna vicuna closed this as completed Aug 28, 2001
@vicuna vicuna added the bug label Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vicuna