When you try to access the contents of a specific memory address, the only thing that can happen is a segmentation fault.
I experimented with this:
#!/usr/bin/perl
BEGIN {
$| = 1;
$^W = 1;
}
use strict;
use autodie;
use warnings FATAL => 'syntax';
use Data::Dumper::Concise;
use POSIX;
use POSIX::RT::Signal qw/sigwaitinfo sigqueue/;
use threads;
use Scalar::Util qw/refaddr/;
use Devel::Pointer::PP;
POSIX::sigprocmask( POSIX::SIG_BLOCK, POSIX::SigSet->new(&POSIX::SIGRT
+MIN) );
my $thr = threads->create( \&_thread );
sub _thread {
my $sigset = POSIX::SigSet->new(&POSIX::SIGRTMIN);
my $info = sigwaitinfo($sigset);
}
my $address = 5;
refaddr( \$address );
my $new_address = \$address;
$$new_address = $$new_address * 4;
sigqueue( $$, &POSIX::SIGRTMIN, $address );
$thr->join();
print Dumper($address);
my $smash = unsmash_sv( 0 + $address );
print Dumper($smash);
exit(0);
-
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.
|