Re: [RFC, gdbserver] Avoid defining linux_read_offsets when the target does not need it

Mike Frysinger
2013-05-15T16:06:59Z

[-- Attachment #1: Type: Text/Plain, Size: 881 bytes --]

On Wednesday 15 May 2013 07:25:34 Luis Machado wrote:
> uClibc-based targets can load their programs in an offset in memory, and
> this information has historically been communicated to gdbserver via
> ptrace with the following options: PT_TEXT_ADDR, PT_DATA_ADDR and
> PT_TEXT_END_ADDR.

well, not to be pedantic, but this is for FLAT programs, not uClibc

> We have a target that uses loadmaps as opposed to the above mechanism.
> It is just another ptrace request, but it doesn't use linux_read_offsets
> at all.

you mean FDPIC ? gdb already supports that and uses a different set of ptrace
requests for that. ideally, gdb nor gdbserver should not be tied to a specific
file format (what format it happened to be compiled for). instead, gdbserver
should support all formats and then gdb detects the format and changes its
requests based on that.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]