| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
| |
The term gdb-client is deceptive - although it parallels the gdb-server name,
it is actually a full fledged gdb version. I want to use it to debug uClibc
core files on my host system. Although I haven't got that to work yet, I wasted
time figuring out how to do build gdb for the host not realizing it already had
a target. With this documentation change, things would have been a lot clearer
to me.
|
| |
|
|
|
|
| |
you want to debug NPTL binaries, you'll need the latest and greatest. Patches for 6.3 will be forward ported where applicable later this week.
|
| |
|
|
|
|
|
| |
apps with a deployed cross toolchain. Should probably do ltrace as well...
Also, add another compat symlink for cross gdb.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
general case, therefore, combine the toplevel Makefile options
such as setting TARGETS into the per-package *.mk file
|
|
|
|
|
|
|
|
|
|
|
|
| |
0000050: gdb_server and gdb_client fixes and split
Here is a patch with 2 issues.
gdbserver does not depend on ncurses (just the full gdb needs it)
Split out gdb client config option, to be separate from gdbserver. If you
build gdb client for the host once it does not need to be rebuilt when the rest
of libs change. So I build it and save it off.
|
| |
|
| |
|
| |
|
| |
|
|
-Erik
|