Have you guys considered, just possibly, just maybe, for one moment that you are actually incorrect about this? And that actually you aren't fully understanding what the script does?

Yes, except that NONE of those will magically extract the source.

Magic isn't required, we're programmers.

Ok, fine, here is magic, http://www.tssc.de/products/tools/memdump/

Have you guys considered, just possibly, just maybe, for one moment that you are actually incorrect about this? And that actually you aren't fully understanding what the script does?

No, the script is plain as day.

And what addresses would you tell memdump to dump?

And as my discussion with ikegami shows, I am *not* claiming it's impossible to get the script. The very page from which you download the script explains that someone CAN get the script. Pointing to memdump is not enough. And pointing to file dumping utilities is not only not enough, it's likely misguided.

Unless someone actually widely posts a step-by-step tutorial on how to get around perlc (just showing some gdb commands a'la ikegami is not enough, as it will only help people who know how to use gdb), then I still think perlc can be useful. This is, I suppose, hard to perceive from the software guru perspective, but just think about how hard it is to even explain the command-line to most computer users and your perspective might change.

And if someone posts such a step-by-step tutorial, then I suppose I'll have to update perlc so that tutorial doesn't work anymore, and the arms race begins! ;-)