From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: yao@codesourcery.com
Cc: vapier@gentoo.org, gdb-patches@sourceware.org
Subject: Re: [RFA 4/8] New port: TI C6x: Read loadmap from gdbserver
Date: Mon, 08 Aug 2011 08:30:00 -0000 [thread overview]
Message-ID: <201108080828.p788SSjq018524@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <4E3F4E05.6010409@codesourcery.com> (message from Yao Qi on Mon, 08 Aug 2011 10:46:29 +0800)
> Date: Mon, 08 Aug 2011 10:46:29 +0800
> From: Yao Qi <yao@codesourcery.com>
>
> On 08/08/2011 08:30 AM, Mike Frysinger wrote:
> > On Monday, July 25, 2011 00:27:50 Yao Qi wrote:
> >> On 07/22/2011 10:16 AM, Mike Frysinger wrote:
> >>>> +#if defined __DSBT__
> >>>> +static int
> >>>
> >>> rather than being tied to the exec format that *gdbserver* is being
> >>> built as, shouldnt this be bound to the ptrace defines being available
> >>> ? how abut using "#ifdef PTRACE_GETDSBT" ?
> >>
> >> Yeah, that makes sense. Done.
> >
> > i think you missed a spot. one place uses __DSBT__ while another uses
> > PTRACE_GETDSBT.
>
> Yes, I thought it is not quite related to PTRACE stuff, so I didn't
> change that. I agree that we should use macros in a consistent way. I
> replace PTRACE_GETDSBT and __DSBT__ with PT_GETDSBT, because PT_GETDSBT
> is defined in sys/ptrace.h, but PTRACE_GETDSBT is defined in asm/ptrace.h.
Well, that leads to the following funny situation:
> +#if defined PT_GETDSBT
You check for PT_GETDSBT here...
> +static int
> +linux_read_loadmap (const char *annex, CORE_ADDR offset,
> + unsigned char *myaddr, unsigned int len)
> +{
> + int pid = lwpid_of (get_thread_lwp (current_inferior));
> + int addr = -1;
> + struct target_loadmap *data = NULL;
> + unsigned int actual_length, copy_length;
> +
> + if (strcmp (annex, "exec") == 0)
> + addr= (int) PTRACE_GETDSBT_EXEC;
> + else if (strcmp (annex, "interp") == 0)
> + addr = (int) PTRACE_GETDSBT_INTERP;
> + else
> + return -1;
> +
> + if (ptrace (PTRACE_GETDSBT, pid, addr, &data) != 0)
...but use PTRACE_GETDSBT here.
Now the kernel vs. libc headers issue has always been a contentious
one on Linux. But I think you should use the PTRACE_-prefixed names
in your code since those are the "official" Linux names, since Linux
was intended to be System V compatible. The PT_-prefixed names are
really only for compatibility with BSD (So I don't really understand
why people keep adding them for ptrace(2) requests that no BSD variant
ever had).
next prev parent reply other threads:[~2011-08-08 8:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 2:09 Yao Qi
2011-07-20 14:32 ` Tom Tromey
2011-07-21 7:32 ` [RFA 9/8] New port: TI C6x: Document on qXfer:fdpic:read packet Yao Qi
2011-07-22 12:22 ` [RFA 4/8] New port: TI C6x: Read loadmap from gdbserver Mike Frysinger
2011-07-25 7:23 ` Yao Qi
2011-08-03 1:29 ` ping: " Yao Qi
2011-08-03 8:59 ` Eli Zaretskii
2011-08-08 0:30 ` Mike Frysinger
2011-08-08 2:47 ` Yao Qi
2011-08-08 8:30 ` Mark Kettenis [this message]
2011-08-08 13:05 ` Yao Qi
2011-08-08 14:01 ` Mark Kettenis
2011-08-08 13:32 ` Pedro Alves
2011-08-09 3:12 ` Yao Qi
2011-08-10 12:37 ` Mark Kettenis
2011-08-10 14:03 ` Pedro Alves
2011-08-10 14:08 ` Pedro Alves
2011-08-14 16:11 ` [committed] " Yao Qi
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=201108080828.p788SSjq018524@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.org \
--cc=yao@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