Front page | perl.perl5.porters |
Postings from May 2012
On Sun Apr 02 22:51:44 2000, RT_System wrote: > On Sun, Apr 02, 2000 at 11:05:41AM +0100, Alan Burlison wrote: > > My current understanding is that this patch broke DBD::Oracle on Linux - > > I'm not quite sure why. > > I'll happily help as far as I can if you send me details. > > (Oracle does very weird things with it's libraries, and then does > different weird things in the following release). > > > I can see a potential problem if a module uses > > call_atexit(), and that then uses a bit of XS that has already been > > dlclosed, but for DBD::Oracle this doesn't seem to be the case. > > > > I (respectfully!) disagree with Sarathay's assertion that dlclosing() > > stuff when the interpreter exits is an 'unnecessary overhead' - it is an > > *essential* part of the cleanup, much in the same way as freeing up > > everything that has been malloced is. It is alright to not free and not > > dlclose if you know that the process is going to exit anyway, but in the > > case of an embedded perl interpreter this is not necessarily the case. > > I think Sarathy meant it's an 'unnecessary overhead' when _not_ embedding. > > > I'd like to get the dlclose stuff into a state where it on by default, > > When embedding, yes. > > > as not having it there generates a particulary abstruse type of bug - it > > took the best part of a year to figure out why mod_perl dumped core when > > built with APXS. > > > > I'd like some informed suggestions of the best way of doing this > > whithout causing collateral damage - anyone have any ideas? > > Do dl_unload_all_files() if Perl_destruct_level > 0. > > Tim. > I can't find the context behind this report. There.. seems to be a solution for the poster's issue at the end, but does anyone know if this is still an issue? Does anyone know what the issue _was_? : / --- via perlbug: queue: perl5 status: open https://rt.perl.org:443/rt3/Ticket/Display.html?id=2968Thread Previous | Thread Next