$ perl perlc.pl a.pl -key password -exe a Out: a.c Exe: a $ gdb a ... (gdb) start Temporary breakpoint 1 at 0x8062cc5 Starting program: /tmp/eric/b/a Temporary breakpoint 1, 0x08062cc5 in main () (gdb) disassemble Dump of assembler code for function main: ... 0x08062df0 <main+302>: movl $0x1,0x4(%esp) 0x08062df8 <main+310>: movl $0x8167020,(%esp) 0x08062dff <main+317>: call 0x8075b30 <Perl_eval_pv> ... End of assembler dump. (gdb) break *0x08062dff Breakpoint 2 at 0x8062dff (gdb) continue Continuing. Breakpoint 2, 0x08062dff in main () (gdb) printf "%s", 0x8167020 # Super secret! print("Hello World\n");
Took me 6 minutes to figure out, and I've never used gdb or this assembler language.
If bleached, follow up with unbleach.pl.
Update: Oops, I have used gdb to get a backtrace of a segfaulting process. I never used any of the commands uses here, though.
In reply to Re^16: What happened to perlcc? (perlc script extractor)
by ikegami
in thread What happened to perlcc?
by rgiskard
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |