From: Daniel Jacobowitz <drow@mvista.com>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] auxv support via xfer_partial, for core files and /proc
Date: Wed, 21 Jan 2004 22:13:00 -0000 [thread overview]
Message-ID: <20040121221353.GA3324@nevyn.them.org> (raw)
In-Reply-To: <200401212206.i0LM6gP1025948@magilla.sf.frob.com>
On Wed, Jan 21, 2004 at 02:06:42PM -0800, Roland McGrath wrote:
> > Roland, FYI, there is already this patch:
> > http://sources.redhat.com/ml/gdb-patches/2003-11/msg00204.html
>
> Thanks for the pointer. I have some comments below comparing the two patches.
>
> > What you should definitly do is add yourself to the write-after-approval
> > list (don't forget to the ChangeLog and to post the committed change).
>
> Done.
>
>
> Here are the notable differences between the two patches.
>
>
> 1. My patch includes the changes affecting gcore:
>
> * procfs.c (procfs_make_note_section): If we can read
> TARGET_OBJECT_AUXV data, add an NT_AUXV note containing it.
> * linux-proc.c (linux_make_note_section): Likewise.
>
> This is not something your patch tries to address. I think we want those
> changes regardless of the implementation details for TARGET_OBJECT_AUXV.
This could be an independent patch, couldn't it? In the interest of
progress, you may wish to submit it separately. Of course it would
have to come after rather than before... so maybe not.
> 5. Your implementation uses pread unconditionally. Mine doesn't bother to
> use pread even when it's available, and just uses lseek + read. Full
> portability, including things like older glibcs running on newer
> kernels, requires using configure tests for pread. I did not bother
> with that because in the real-world case, there will just be one read
> from offset 0 and so lseek won't even be called, just open+read+close.
The configury is already there, FYI. Grep for HAVE_PREAD64 in linux-proc.c.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-21 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 10:45 Roland McGrath
2004-01-21 15:48 ` Andrew Cagney
2004-01-21 22:06 ` Roland McGrath
2004-01-21 22:13 ` Daniel Jacobowitz [this message]
2004-01-21 22:16 ` Roland McGrath
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=20040121221353.GA3324@nevyn.them.org \
--to=drow@mvista.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=roland@redhat.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