Uhm, i have no 64 bit box here. I'm a traveller these days :P I have pushed some new stuff into the repository fixing a minor bug in x86-64 and some enhacements for the python support.
btw I would like to know if the bug is related to rabin or radare itself. Try running "rabin -isr $FILE" and provide an stacktrace of it or something like that :) Remember to put -g in your CFLAGS before building it to give me a better idea why its crashing. rabin theorically works fine with elf32 and elf64, and it has been tested only in 32 bit boxes (sparc, mips, intel). Thanks for the bug report. I plan to spend more time on the 64 bit support for 1.0, but i think the debugger layer needs more work. Because..for example if you debug a 32 bit program from a 64bit box, the debugger will think that its 64 bit one and will provide its interface instead of the 32 bit one which is incorrect. This bug also happens in gdb. And the only solution is to recompile radare using a 32 bit box. Thanks! On Thu, 31 Jul 2008 21:03:41 +0200 Sebastian Reichel <[EMAIL PROTECTED]> wrote: > Hi, > > There is a segmentation fault in linux x86-64 if file.flag is enabled: > > [EMAIL PROTECTED] ~ % radare /bin/ls > open ro /bin/ls > Message of the day: [...] > Automagically flagging file... > 91 imports added > 4 symbols added > 28 sections added > 635 strings added > zsh: segmentation fault radare /bin/ls > > Without flagging enabled radare does start correctly ;) > > This time you will definiv get the first place @ Defcon CTF :) > > -- elektranox > > Am Donnerstag, den 31.07.2008, 19:17 +0200 schrieb pancake: > > I have unidirectionally decided to release 0.9.9. > > > > Tomorrow I get a travel to London for a week, and I'll be out for two > > weeks. I just wanted to make an stable release to make all the users > > happy with it. > > > > Leech it from here: > > http://radare.nopcode.org/get/radare-0.9.9.tar.gz > > > > Short changelog: > > http://radare.nopcode.org/?p=down > > > > Long changelog: > > http://radare.nopcode.org/get/changelog-0.9.9 > > > > This new release comes with at least 40 changesets with interesting > > fixups on stability, performance and features. > > > > We're close to 1.0, but i dont plan to release it before setember. So, > > take this release, play with it, enjoy it, and let me know what you > > miss. > > > > I plan to start refactoring and cleaning up the source code beyond the > > 1.0. There are some ugly stuff in the debugger that needs to be fixed > > and I want to highly reduce the LOCs to make the core more consistent > > internally. > > > > But currently I think its ready for the mass use :) > > > > If you have any question. PLEASE ask. i have no time for writing > > documentation, but i think the core is almost easy to learn if you with > > some basic knowledge of the functionalities. > > > > I am thinking on a 1.0 party in Barcelona... so stay tuned for some > > reebs and t-shirts ;) > > > > Have fun!! > > > > --pancake > > _______________________________________________ > > radare mailing list > > [email protected] > > http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org _______________________________________________ radare mailing list [email protected] http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
