On Sat, Jan 28, 2006 at 09:48:17PM +0200, Marko Asplund wrote: > hi > > I've been doing some more tests concerning this issue and it seems > that it only appears with the combination of Oracle Instant client > libraries, Perl configured with -Dusemymalloc on RHEL 3. When I > configure Perl without -Dusemymalloc everything works fine.
By which I presume you mean it appears to work fine because it doesn't segfault. An underlying problem, such as memory corruption, may still be present, just not causing any visible problem in you application. (Sorry to be pessimistic.) There are memory allocation debugging tools that may help to isolate the original problem and so give some confidence that it's not present in the other configurations. > The issue doesn't appear with Oracle10g full client on RHEL 3 or with > OIC on RHEL 4, Solaris 8 or HP-UX 11i v1. Thanks for doing the legwork to narrow it down. > I've reported this issue to Oracle but does anyone have clues on what > is causing this or suggestions on how to get this fixed on the Perl > side? I'd really need to use -Dusemymalloc and Oracle Instant Client. Why? The Perl -DPERL_POLLUTE_MALLOC option may be of use. But you might just be trading one can of worms for another. Also, try http://www.data-plan.com/public/DBD-Oracle-1.17-RC6.tar.gz I don't think there are any relevant changes but I'd be interested to know if you get similar behaviour on the various systems. Tim.
