Mmmh you are right. I dont get any segfault, but an error for syntax,
but at the end this is a bug in the macro parser. You should quote
the macro to avoid interpretting internal escape characters, greps,
pipes and so on. I want to write some unit tests to test all the macro
and internal scripting stuff.
I have uploaded in the radare2 repo a patch that allows to grep more
than one keyword at a time. I will backport this patch to radare1.
The syntax is:
pd~call!jmp
(split every keyword with the '!' character)
Thanks for the bug report. Next time i will check twice the macros
before sending them to the list ;)
--pancake
Anderson Lizardo wrote:
On Sat, Mar 14, 2009 at 8:52 AM, Nibble <[email protected]> wrote:
Hi,
All the issues should be fixed now in rabin :)
Ok, I tried tip 914 now, and it resolved the long symbol name issue,
but radare still aborts with the macro definition:
$ radare lib.so
...
[0x0003AF30]> (for-each-call x,()`...@$0~call[1]#$@`)
*** stack smashing detected ***: radare terminated
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x48)[0xb7869138]
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x0)[0xb78690f0]
radare[0x808d071]
[0x314e5a5f]
...
Aborted
Regards,
_______________________________________________
radare mailing list
[email protected]
http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
