In fact, I discovered that even when ttm is compiled without optimization options, it causes segmentation faults when run in a continuous loop: while (true); do ./ttm; done
(1st run okay...) (2nd run -- out of memory) (3rd run -- segmentation fault) Predictably, the use of threads has introduced time as an input to the algorithm -- yet another example why threads should be avoided in program design. -Ivan "Jim Ursetto" <[EMAIL PROTECTED]> writes: > Ran okay here. Do you have more stats about your environment, chicken > version, a less complicated program that can reproduce the problem, > etc.? > > $ csc -o ttm ttm.scm > $ ./ttm > test > Load error in (define aa (with-timeout 3 (lambda () (do () (#f) > #t)))):(timeout) in (define aa (with-timeout 3 (lambda () (do () (#f) > #t)))) > let's do some garbage > enough garbage > done > let's do some garbage > enough garbage > _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
