On 2006-02-01, at 00.45, Tim Bunce wrote:
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.)
You're right,
On Wed, Feb 01, 2006 at 01:52:02PM +0200, Marko Asplund wrote:
On 2006-02-01, at 00.45, Tim Bunce wrote:
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.
I'am not really
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
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. The issue
doesn't appear
hi
I'm having problems with DBD::Oracle built with Oracle Instant Client
on Linux (RHEL 3 U6). Occasionally when i run my application from
the command line the process receives a segmentation fault and
sometimes it terminates with an 'Out of memory' message.
I've been able to reproduce
