Re: Code review for thread safeness

[Kevin Ryde]

Marius Vollmer <address@hidden> writes:
>
> If there might be non-local exits, scm_frame_critical_section can be
> used instead.

If an error occurs and a lazy-catch executes, is the mutex unlocked
for that handler?

> Also, there are probably many more places that need to become critical
> sections.  We need to find them and use SCM_CRITICAL_SECTION_START/END
> or scm_frame_critical_section, as appropriate.

The ones I've spotted are (I might have posted this before),

        gethostbyname
        getpwuid
        setpwent (etc)
        getgrgid
        setgrent (etc)
        setlocale
        scm_mem2symbol 

or scm_i_mem2symbol or whatever it is now.  I probably won't get a
chance to actually do anything about these.