Re^2: How to access the contents of a specific memory address?

That's a feature, because it means you can't get segmentation fauls or bus errors if you stick to pure Perl code (no C code involved).

I disagree.

perl -e "print unpack('p', pack('J', 1))"
[download]

Comment on Re^2: How to access the contents of a specific memory address? Download Code

Replies are listed 'Best First'.
Re^3: How to access the contents of a specific memory address? by pat_mc (Pilgrim) on Jul 29, 2012 at 19:50 UTC
Strange: When I try this, I get a segmentation fault. Am I overlooking some important detail? `$ perl -e 'print unpack("p", pack("J", 1))' Segmentation fault` [download]	[reply] [d/l]
Re^4: How to access the contents of a specific memory address? by Your Mother (Archbishop) on Jul 29, 2012 at 23:10 UTC
Am I overlooking some important detail? Simple logic. :P `Proposition: You can't get segfaults with pure Perl. Response: I disagree: code sample` [download]	[reply] [d/l]
Re^5: How to access the contents of a specific memory address? by pat_mc (Pilgrim) on Jul 30, 2012 at 19:12 UTC
Not sure I am finding your response very helpful. At any rate I'll pass your comment on to my bash shell that generated the output I quoted. Why can't Perl give rise to a segmentation fault? And what then is the meaning of the system output the given line of code produces?	[reply]
Re^6: How to access the contents of a specific memory address? by bulk88 (Priest) on Jul 30, 2012 at 20:26 UTC