in reply to Apache, mod_perl, C++, XS and Shared Memory

You need to post some code. Without it, everything's just a guess.

mod_perl doesn't deny access to shared memory. You can use GTop to get a process shared memory size and total size. For example,

#!/usr/bin/perl use strict; use warnings; use GTop (); my $gtop = GTop->new; my $proc_mem = $gtop->proc_mem(2872); print "Shared memory of the current processes: ", my $share = $gtop->proc_mem($$)->share, "\n"; print "Total memory size of current processes: ", my $size = $gtop->proc_mem($$)->size, "\n";
For more help, see:
mod_perl intro
Measuring_the_Memory_of_the_Process

Update: This will get the shared memory and size for a single process:

#!perl use strict; use warnings; use GTop (); use Data::Dumper::Concise; my $gtop = GTop->new(@ARGV); my $pid = 2518; my $proc_mem = $gtop->proc_mem($pid); for ($pid) { warn Dumper my $share = $proc_mem->share, my $size = $proc_mem->size; }

Replies are listed 'Best First'.
Re^2: Apache, mod_perl, C++, XS and Shared Memory
by Anonymous Monk on Sep 13, 2010 at 10:56 UTC

    Thank you all for you effort, I finally solved it.
    The problem was that the linked library expected some environment variable to be set; and I forgot to set them :-(
    Now after having these variables set everything works fine and it had nothing to do with the shared memory segments.

    --- closed ---