in reply to Re^2: Accessing Memory-mapped I/O
in thread Accessing Memory-mapped I/O

You're doing two completely different thing between the Perl code and the C code. Does the C code still work when using seek? Does the Perl code work when using (for example) File::Map?

Replies are listed 'Best First'.
Re^4: Accessing Memory-mapped I/O
by Anonymous Monk on Oct 31, 2019 at 17:38 UTC

    I have not tried C code using seek. Nor have I tried File::Map on my limited system as I don't have access to File::Map. CPAN is not functioning to install it.

[reply]

      What system is this (OS, 32 or 64 bit etc), and what version of perl? I can't reproduce the Perl issue you describe on Linux Mint 18.3 64-bit, nor Raspbian (armv7l) 32-bit. Both return without any warning or error (even after adding strict and warnings).

      On the 64-bit platform I've got Perl 5.26.1, and on the 32-bit one, I've got Perl 5.30.0.

      Update: I agree with Corion, the Perl code doesn't reflect at all what the C code is doing.

[reply]
[d/l]
[select]

        Stievieb- thank you for trying the code on your systems.

        I am using altera-ltsi 4.1.33 on an armv7l (32-bit) and perl 5.2.22.

        I understand that the Perl code isn't doing the same thing as the C-code. My question really is whether there is something with my Perl build (or code) that would prevent me from accessing memory outside the system ram. Other processes can access that ram without an issue.

[reply]

In Section Seekers of Perl Wisdom