Hi
On Apr 14, 2010, at 9:40 PM, Robin Vossen <[email protected]>
wrote:
Hello Developers,
I just checked out the newest repo (this time I remembered to do the
make clean)
And I was about to check some of the new radare interface. The
debugging thing.
So I did the following:
radare2 dbg:///bin/ls and I just entered the first command to be dbt.
SegFault.
I recommend to use the -d flag, so you get some evals configured
properly to debug.
Tomorrow I will have a look at this issue, but first try:
r2 -d ls
> dbt
I wanted to get a backtrace with gdb but I got an error.
Thus I thought Ill do the following : radare2 dbg://"radare2 dbg:///
bin/ls"
When I did hit dbt now I just got an Terminal on Drugs.
Are you using archlinux? The gdb there is broken. I cannot use gdb as
process launcher, so I hook a sleep somewhere and do the attach with
gdb --pid. Hope this helps.
A valgrind log sometimes do the job :)
I cant do a Backtrace right now as I get an error in GDB. I'd need to
check the Compiler flags of gdb (looks like Threading is disabled) but
I cant be asked at the moment as its quite late.
Hope this already helped a bit.
Thanks! Reporting is always welcome.
ATM I'm working on the debugger side, porting it to windows, you can
read the changelog.
I also started to write a user documentation in markdown using sw. I
will make it public soon.
Cheers,
_______________________________________________
radare mailing list
[email protected]
http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
