On Sun, Aug 12, 2001 at 10:29:53AM -0400, Daniel Eischen wrote:
> sigprocmask() behaves the same as pthread_sigmask(). pthread_sigmask()
> needs to obtain the current thread. In obtaining the current thread,
> the threads library must be initialized. In initializing the threads
> library malloc() is called. Wash, rinse, repeat.
We have a winner. This is the top of the (very long) call stack from the
mozilla core file (which I admittedly should have examined earlier):
#11913 0x2863ebda in _thread_init () from /usr/lib/libc_r.so.5
#11914 0x2863e7a3 in _get_curthread () from /usr/lib/libc_r.so.5
#11915 0x28633539 in pthread_sigmask () from /usr/lib/libc_r.so.5
#11916 0x2863f250 in sigprocmask () from /usr/lib/libc_r.so.5
#11917 0x286c9db5 in malloc () from /usr/lib/libc.so.5
#11918 0x2863a980 in _pq_alloc () from /usr/lib/libc_r.so.5
#11919 0x2863ebda in _thread_init () from /usr/lib/libc_r.so.5
#11920 0x2863e7a3 in _get_curthread () from /usr/lib/libc_r.so.5
#11921 0x28633539 in pthread_sigmask () from /usr/lib/libc_r.so.5
#11922 0x2863f250 in sigprocmask () from /usr/lib/libc_r.so.5
#11923 0x286c9db5 in malloc () from /usr/lib/libc.so.5
#11924 0x2863a980 in _pq_alloc () from /usr/lib/libc_r.so.5
#11925 0x2863ebda in _thread_init () from /usr/lib/libc_r.so.5
#11926 0x2863c063 in pthread_mutex_lock () from /usr/lib/libc_r.so.5
#11927 0x2861556d in __register_frame_info () from /usr/lib/libstdc++.so.3
#11928 0x28662fa2 in _init () from /usr/lib/libc.so.5
#11929 0x2866062d in _init () from /usr/lib/libc.so.5
#11930 0x2806de10 in _rtld () from /usr/libexec/ld-elf.so.1
So, in answer to the question, "am I doing something boneheaded, or is this
an undocumented subtle interaction," I'll give partial credit to both.
Thank you very much for your assistance.
-Michael Robinson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
