Re: porting to amd64-freebsd

Bruce Mitchener <[email protected]>
Newsgroups gmane.comp.lang.dylan.gwydion.devel
Message-ID <CA+esKjMBhOJRCgxpuN6-wzvzJYzE=Cu0Vz-bu7ROkjXA4d5+aw@mail.gmail.com>
Usually you can do this via ulimit at the shell level:

    ulimit -s 16384

 - Bruce


On Mon, Jan 14, 2013 at 6:19 AM, <[email protected]> wrote:

> Hello,
>
>
> On Sat, 12 Jan 2013 22:49:17 +0900, Hannes Mehnert <[email protected]>
> wrote:
>
>> For that I needed to increase the stack size - maybe you need to do that?
>>
> when I encounter to SEGV, the $rsp points stack guard address.
> perhaps cause of SEGV is the stack shortage.
>
> I found this article.
> http://lists.freebsd.org/**pipermail/freebsd-hackers/**
> 2008-January/022916.html<http://lists.freebsd.org/pipermail/freebsd-hackers/2008-January/022916.html>
> it says
> | There is no way in FreeBSD to do the same for initial stack size for the
> | main thread.  No runtime, no linktime, no nada nichego.  Apparently, the
> | only way to increase it is to recompile your threaded library, which will
> | have a system-wide effect.
>
> It seems  I need some trick to solve it.
> --
> HIROSHI OOTA
>
>
>
>> I think also it started to fail after some changes to the C runtime in
>> 2012.
>> You might first want to check whether the C runtime works fine on
>> FreeBSD and 32 bit (single and multi-threaded).
>>
>>
>> Hannes
>> ______________________________**_________________
>> hackers mailing list
>> [email protected]
>> https://lists.opendylan.org/**mailman/listinfo/hackers<https://lists.opendylan.org/mailman/listinfo/hackers>
>>
> ______________________________**_________________
> hackers mailing list
> [email protected]
> https://lists.opendylan.org/**mailman/listinfo/hackers<https://lists.opendylan.org/mailman/listinfo/hackers>
>

_______________________________________________
hackers mailing list
[email protected]
https://lists.opendylan.org/mailman/listinfo/hackers
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.