i have a daemon process which uses a dlopened module, which changes from
time to time. on SIGHUP to daemon dlcloses said module, and reopens what
is (hopefully) the fresh copy, resolves it function ptrs again, and
continues. this seems to work o.k except for some odd behavior i've seen
with libtool install mode :
using cp for the install either :
a) causes dlclose to core dump
b) does not allow the process to pick up the 'new'
copy
using install always results in the 'right' behavior
i'm running this on 6 or 7 different platforms, and have compiled with
-avoid-versioning to that is not the issue.
can anyone comment on why using cp instead of install should make a
difference? i've even notice weird behavior using different install
programs.
thanks for the advice.
-ara
--
====================================
| Ara Howard
| NOAA Forecast Systems Laboratory
| Information and Technology Services
| Data Systems Group
| R/FST 325 Broadway
| Boulder, CO 80305-3328
| Email: [EMAIL PROTECTED]
| Phone: 303-497-7238
| Fax: 303-497-7259
====================================
_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
