This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH/RFC] auxv entries


On Mon, Sep 15, 2008 at 10:22:37PM +0200, Mark Kettenis wrote:
> Here is the promised diff.  Tested on Linux on amd64 (which doesn't
> say a lot since it is little-endian).
> 
> ok?

I think the layout of the aux vector is a strange combination of an
architecture property and a target property.  We can read it via
gdbserver too; the remote protocol manual says it's just 'Access the
target's "auxiliary vector"'.  The comments on procfs_auxv_parse
imply that it depends on the host GDB in native Solaris debugging.
But on Linux it depends on the debuggee, not the debugger.

Is there some way we can differentiate based on gdbarch or osabi?

-- 
Daniel Jacobowitz
CodeSourcery


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]