Anthony D. Baye <Sha### [at] spamnomorehotmailcom> wrote:
> > The segfault is due to the depth of CSG: each level will stack a few
> > calls... the provisionned stack is not big enough for diving in that data.

> Thanks for responding.

> It's pretty much what I figured, although I had thought it was a signed 16-bit
> overflow somewhere, but 32768 works just fine.

> my solution was to create another container to hold unions of a safe size, but
> it seems that there's a better solution.

> at any rate, it would probably be a good idea to do some error checking on the
> stack size before it overflows and causes a segfault.

In any case, a segmentation fault is not something that a program should do,
so a bug report is in place.

-- 
                                                          - Warp

Post a reply to this message