Looks like a problem related in cons.c
Are you using the debian package? Or a snapshot compiled by you? I
would recommend you to get it from mercurial to ensure that the bug is
not yet fixed in mainstream.
If it is compiled by you, can you provide the gcc version and cflags
used?
To debug the segfault I will use valgrind and gdb. If the binary has
been built with debug info you will get a backtrace using the bt
command in gdb.
If the bug cannot be reproduced by gdb, try by running it in valgrind.
If you can't get it in any of these ways just enable core files and do
some postmortem analysis.
Send those backtraces to the mailing list, so we can point to the
problem.
Btw is this happening on 32 or 64 bits?
Let me know :)
Thanks for reporting
On Nov 4, 2009, at 5:55 AM, "jcyang" <[email protected]> wrote:
Hi,
I'm new to linux revese engineering,and even newer to radare.So I
tried to follow the radare book step by step,but I failed on the
first step.
When I run 'radare -d /bin/ls',the radare failed in the analyze code
section with segment failed.Unexpectedly,when I try to ues
'typescript' to log the error message,radare runs successfully,but
if I exit the typescript mode,then the error message turns out agian.
I am running debian lenny ,radare 2009.07.22.
Whether it is a bug?If it is,what I need to provide to help fix the
bug?
thanks.
_______________________________________________
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
