Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] x86-64 segment registers handling
Date: Tue, 26 Mar 2002 10:14:00 -0000	[thread overview]
Message-ID: <20020326131355.A25917@nevyn.them.org> (raw)
In-Reply-To: <3CA0AF53.8030609@suse.cz>

On Tue, Mar 26, 2002 at 06:26:43PM +0100, Michal Ludvig wrote:
> Hi all,
> this patch synces gdb with recent ABI changes in x86-64 kernel, which 
> added segment registers to user_regs_struct in corefile and ptrace() 
> call. Because it was hard to find all places which could depend on this 
> change I also did a cleanup. I joined most of registers information to 
> one structure at the beginning of x86-64-tdep.c to make it more readable 
>  and maintainable and changed some "anonymous constants" (numbers) to 
> derivatives of #defines.
> Can I commit?
> 
> Index: ChangeLog

> 	* x86-64-linux-nat.c (x86_64_regmap): Swapped
> 	RBX <> RDX, added DS, ES, FD, GS

Can you update gdbserver/linux-x86-64-low.c with these changes, please?

> 	(x86_64_linux_dr_get_status), (supply_gregset),
> 	(fill_gregset): Changed X86_64_NUM_GREGS to
> 	x86_64_num_gregs
> 	* x86-64-tdep.c (x86_64_register_raw_size_table): Delete
> 	(x86_64_register_info_table): Add
> 	(X86_64_NUM_REGS, X86_64_NUM_GREGS): Add
> 	(x86_64_register_raw_size),
> 	(x86_64_register_virtual_type),
> 	(x86_64_register_name),
> 	(_initialize_x86_64_tdep): Changed to reflect new
> 	general x86_64_register_info_table.
> 	(i386_gdbarch_init): gdbarch_register_bytes is now set
> 	dynamicaly during initialization.

Also, it appears that you changed the layout of GDB's register cache
for x86-64.  At this time that means you also changed the remote
protocol.  regformats/reg-x86-64.dat also needs to be updated.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2002-03-26 18:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-26  9:26 Michal Ludvig
2002-03-26 10:00 ` Andrew Cagney
2002-03-26 10:09   ` Michal Ludvig
2002-03-27  4:18   ` Michal Ludvig
2002-03-27  6:23     ` Andrew Cagney
2002-03-26 10:14 ` Daniel Jacobowitz [this message]
2002-03-26 10:27   ` Michal Ludvig
2002-03-26 10:35     ` Daniel Jacobowitz

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=20020326131355.A25917@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mludvig@suse.cz \
    /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