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! ;-)

Unless someone actually widely posts a step-by-step tutorial on how to get around perlc

Seriously? How much faster than 6 minutes do you want it to be?

Furthermore, googling "perlc extractor" finds the thread with the perlc script extractor as the second match.

and the arms race begins! ;-)

Race? You haven't made any move and it's been at least 5 months.

Besides, it's not an arms race; it's trying to avoid having people getting fooled into thinking perlc is anything but a pile of garbage.

If the solution is for you to actually write something that works, perfect! Unfortunately, you'd rather defend its current state.

just showing some gdb commands a'la ikegami is not enough, as it will only help people who know how to use gdb

Huh? To the contrary, it shows how to get the script without any knowledge of gdb whatsoever. One just have to repeat the commands. A script kiddie can do that.

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! ;-)

Nice try