comment on

My hunch is that there's something in your code (which you haven't provided) that's causing the problem. I believe the following Inline::C script demonstrates that we can pass strings (in both directions) via the stack that are considerably larger than 64kb. At least that's what it demonstrates on my Win32 box - as the script ouptputs "8000000".

If the same script produces the same output on your box, then I think we can conclude that the problem you're facing is something other than a stack size limit.

use warnings;
use strict;

use Inline C => Config =>
    BUILD_NOISY => 1;

use Inline C => <<'EOC';

void foo(char * htmFile, int len) {
     dXSARGS;
     sp = mark;
     XPUSHs(sv_2mortal(newSVpv(htmFile, len)));
     PUTBACK;
     XSRETURN(1);
}

EOC

my $len = 8000000;
my $z = 'z' x $len;

my $copy = foo($z, $len);

print length($copy), "\n";
[download]

Cheers,
Rob

In reply to Re: converting a C pointer to a perl reference by syphilis
in thread converting a C pointer to a perl reference by jithoosin

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks