Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

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

by pat_mc (Pilgrim)
on Jul 30, 2012 at 19:12 UTC ( #984493=note: print w/ replies, xml ) Need Help??


in reply to Re^4: How to access the contents of a specific memory address?
in thread How to access the contents of a specific memory address?

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?


Comment on Re^5: How to access the contents of a specific memory address?
Re^6: How to access the contents of a specific memory address?
by bulk88 (Priest) on Jul 30, 2012 at 20:26 UTC
    You are asking why does null pointer (or something near null pointer such as memory address 1), causes a segmentation fault. It is that way because null pointer has caused segmentation fault since the begin of computers in the 20th century, decades ago ( see http://en.wikipedia.org/wiki/Segmentation_fault and http://en.wikipedia.org/wiki/Null_pointer#Null_pointer). You may be also asking, why does an example that is intended to crash the perl interp crash the perl interp. The answer to that is, because it is an example to crash the perl interp. A different question is, why does the perl interp crash from that example, read my second sentence.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://984493]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (14)
As of 2014-07-22 11:32 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (110 votes), past polls