Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how to compile arm target? #1

Open
Frogmarch opened this issue Apr 7, 2016 · 2 comments
Open

how to compile arm target? #1

Frogmarch opened this issue Apr 7, 2016 · 2 comments

Comments

@Frogmarch
Copy link

how to compile arm target?

@Frogmarch
Copy link
Author

I compile with:
./configure --target=arm-linux
make
sudo make install

and run:
arm-linux-gdb vmlinux RAMEDUMP

but still can not debug the ramdump:

GNU gdb (GDB) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-unknown-linux-gnu --target=arm-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/rjxu/work/ramdump/vmlinux...done.
warning: Couldn't find general-purpose registers in core file.
warning: Couldn't find general-purpose registers in core file.
PC not available
#-1 in ?? ()

this vmlinux and ramdump can be parsed by crash utility

@alesax
Copy link
Owner

alesax commented Apr 7, 2016

First - in which format this ramdump is? Is it supported by libkdumpfile?

Second - I am sorry to say that ARM is not yet supported. That means at least small part of code handling storing of registers to stack, and the registers from dump.

Third - see the discussion on gdb & gdb-patches mailing list. It can't be used that way, you'd need (after the previous topics are resolved) to run something like "target kdump /file/with/dump".

Fourth - this original gdb-kdump project is discontinued, because it wasn't accepted to gdb upstream. What continues further is development of Python binding to "gdb target". That will offer perhaps more comfortable way of implementing i.e. different CPU architecture or different kernel version handling. You may want to see for yourself:

https://github.com/jeffmahoney/gdb-python/tree/python-working-target
https://github.com/jeffmahoney/crash-python

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants