From: Mike Frysinger <vapier@gentoo.org>
To: lgustavo@codesourcery.com
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [RFC, gdbserver] Avoid defining linux_read_offsets when the target does not need it
Date: Wed, 15 May 2013 16:06:00 -0000 [thread overview]
Message-ID: <201305151206.57607.vapier@gentoo.org> (raw)
In-Reply-To: <519370AE.50908@codesourcery.com>
[-- 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 --]
next prev parent reply other threads:[~2013-05-15 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 11:25 Luis Machado
2013-05-15 14:14 ` Pedro Alves
2013-05-16 10:34 ` Luis Machado
2013-05-15 14:17 ` Yao Qi
2013-05-15 16:06 ` Mike Frysinger [this message]
2013-05-15 16:26 ` Luis Machado
2013-05-15 17:12 ` Mike Frysinger
2013-05-15 18:08 ` Luis Machado
2013-05-15 18:51 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201305151206.57607.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox