[M3devel] endless exception loop on FreeBSD

[Tony Hosking]

Any chance that the sigjmp buffers are differently-sized with the new  
libc?

On Dec 22, 2007, at 3:05 PM, Olaf Wagner wrote:

> Tony Hosking wrote:
>
>> Hmm. It doesn't ring any bells for me.
>>
>> On Dec 21, 2007, at 7:22 AM, Olaf Wagner wrote:
>>
>>> I'm trying to add pthread support to the FreeBSD4 platform.
>>> My first tentative additions now lead to endless exception loops
>>> once any error is encountered until the stack overflows.
>>>
>>> Does anybody know what's wrong here? I'm not aware that I have
>>> changed anything in this area.
>>
> I seems that I have been linking against a non-reentrant libc. I  
> can now get a little
> farther:
>
> % ./m3-sys/cm3/FreeBSD4/cm3 -help @M3debugthreads
> Stopping from act=0x8a93500
> Stopping act=0x8a93b80
> Stopped act=0x8a93b80
> Stopped from act=0x8a93500
> Processing act=0x8a93500
> Processing act=0x8a93b80
> Starting from act=0x8a93500
> Starting act=0x8a93b80
> Started act=0x8a93b80
> Started from act=0x8a93500
> Stopping from act=0x8a93500
> Stopping act=0x8a93b80
> Stopped act=0x8a93b80
> Stopped from act=0x8a93500
> Processing act=0x8a93500
> Processing act=0x8a93b80
> Starting from act=0x8a93500
> Starting act=0x8a93b80
> Started act=0x8a93b80
> Started from act=0x8a93500
> CStatus failed with errno 2
>
>
> ***
> *** runtime error:
> ***    Unhandled exception: OSError.E
> ***    file "../src/os/POSIX/OSErrorPosix.m3", line 50
> ***
>
> Abort trap (core dumped)
>
> This is the compiler trying to locate cm3.cfg at different locations.
> It doesn't find it and an OSError.E is raised, which should get caught
> in M3File.IsReadable, but isn't. So it seems exception handling is
> broken as soon as I use system threads. Any ideas on this one?
>
> Olaf